Positioning reference signal (PRS) report with discontinuous reception (DRX)

ABSTRACT

Disclosed are techniques for reducing overhead of low layer positioning reports. In an aspect, a user equipment (UE) operating in discontinuous reception (DRX) mode determines that the UE is not expected to wake up during a next DRX ON duration of a DRX cycle; determines, based on one or more factors, whether to wake up during the next DRX ON duration to transmit a positioning measurement report or an uplink positioning reference signal (UL-PRS); and based on the determination: wakes up and transmits the positioning measurement report or the UL-PRS during the next DRX ON duration, or remains in a DRX sleep state and refrains from transmitting the positioning measurement report or the UL-PRS during the next DRX ON duration.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present Application for Patent claims the benefit of U.S.Provisional Application No. 63/024,804, entitled “POSITIONING REFERENCESIGNAL (PRS) REPORT WITH DISCONTINUOUS RECEPTION (DRX),” filed May 14,2020, assigned to the assignee hereof, and expressly incorporated hereinby reference in its entirety.

BACKGROUND OF THE DISCLOSURE 1. Field of the Disclosure

Aspects of the disclosure relate generally to wireless communications.

2. Description of the Related Art

Wireless communication systems have developed through variousgenerations, including a first-generation analog wireless phone service(1G), a second-generation (2G) digital wireless phone service (includinginterim 2.5G and 2.75G networks), a third-generation (3G) high speeddata, Internet-capable wireless service and a fourth-generation (4G)service (e.g., Long Term Evolution (LTE) or WiMax). There are presentlymany different types of wireless communication systems in use, includingcellular and personal communications service (PCS) systems. Examples ofknown cellular systems include the cellular analog advanced mobile phonesystem (AMPS), and digital cellular systems based on code divisionmultiple access (CDMA), frequency division multiple access (FDMA), timedivision multiple access (TDMA), the Global System for Mobilecommunications (GSM), etc.

A fifth generation (5G) wireless standard, referred to as New Radio(NR), calls for higher data transfer speeds, greater numbers ofconnections, and better coverage, among other improvements. The 5Gstandard, according to the Next Generation Mobile Networks Alliance, isdesigned to provide data rates of several tens of megabits per second toeach of tens of thousands of users, with 1 gigabit per second to tens ofworkers on an office floor. Several hundreds of thousands ofsimultaneous connections should be supported in order to support largesensor deployments. Consequently, the spectral efficiency of 5G mobilecommunications should be significantly enhanced compared to the current4G standard. Furthermore, signaling efficiencies should be enhanced andlatency should be substantially reduced compared to current standards.

SUMMARY

The following presents a simplified summary relating to one or moreaspects disclosed herein. Thus, the following summary should not beconsidered an extensive overview relating to all contemplated aspects,nor should the following summary be considered to identify key orcritical elements relating to all contemplated aspects or to delineatethe scope associated with any particular aspect. Accordingly, thefollowing summary has the sole purpose to present certain conceptsrelating to one or more aspects relating to the mechanisms disclosedherein in a simplified form to precede the detailed descriptionpresented below.

In an aspect, a method of wireless communication performed by a userequipment (UE) operating in discontinuous reception (DRX) mode includesdetermining that the UE is not expected to wake up during a next DRX ONduration of a DRX cycle, determining, based on one or more factors,whether to wake up during the next DRX ON duration to transmit apositioning measurement report or an uplink positioning reference signal(UL-PRS), and based on the determination: waking up and transmitting thepositioning measurement report or the UL-PRS during the next DRX ONduration, or remaining in a DRX sleep state and refraining fromtransmitting the positioning measurement report or the UL-PRS during thenext DRX ON duration.

In an aspect, a UE includes a memory, at least one transceiver, and atleast one processor communicatively coupled to the memory and the atleast one transceiver, the at least one processor configured to, whileoperating in DRX mode, determine that the UE is not expected to wake upduring a next DRX ON duration of a DRX cycle, determine, based on one ormore factors, whether to wake up during the next DRX ON duration totransmit a positioning measurement report or an UL-PRS, and based on thedetermination: wake up and cause the at least one transceiver totransmit the positioning measurement report or the UL-PRS during thenext DRX ON duration, or remain in a DRX sleep state and refrain fromcausing the at least one transceiver to transmit the positioningmeasurement report or the UL-PRS during the next DRX ON duration.

In an aspect, a UE includes means for determining, while operating inDRX mode, that the UE is not expected to wake up during a next DRX ONduration of a DRX cycle, means for determining, based on one or morefactors, whether to wake up during the next DRX ON duration to transmita positioning measurement report or an UL-PRS, and based on thedetermination: means for waking up and transmitting the positioningmeasurement report or the UL-PRS during the next DRX ON duration, ormeans for remaining in a DRX sleep state and refraining fromtransmitting the positioning measurement report or the UL-PRS during thenext DRX ON duration.

In an aspect, a non-transitory computer-readable medium storescomputer-executable instructions includes computer-executableinstructions comprising at least one instruction instructing a UEoperating in DRX mode to determine that the UE is not expected to wakeup during a next DRX ON duration of a DRX cycle, at least oneinstruction instructing the UE to determine, based on one or morefactors, whether to wake up during the next DRX ON duration to transmita positioning measurement report or an UL-PRS and based on thedetermination: at least one instruction instructing the UE to wake upand transmit the positioning measurement report or the UL-PRS during thenext DRX ON duration, or at least one instruction instructing the UE toremain in a DRX sleep state and refrain from transmitting thepositioning measurement report or the UL-PRS during the next DRX ONduration.

Other objects and advantages associated with the aspects disclosedherein will be apparent to those skilled in the art based on theaccompanying drawings and detailed description.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings are presented to aid in the description ofvarious aspects of the disclosure and are provided solely forillustration of the aspects and not limitation thereof.

FIG. 1 illustrates an example wireless communications system, accordingto aspects of the disclosure.

FIGS. 2A and 2B illustrate example wireless network structures,according to aspects of the disclosure.

FIGS. 3A, 3B, and 3C are simplified block diagrams of several sampleaspects of components that may be employed in a user equipment (UE), abase station, and a network entity, respectively, and configured tosupport communications as taught herein.

FIGS. 4A to 4D are diagrams illustrating example frame structures andchannels within the frame structures, according to aspects of thedisclosure.

FIGS. 5A to 5C illustrate example discontinuous reception (DRX)configurations, according to aspects of the disclosure.

FIG. 6 illustrates a timeline showing two example DRX occasions andtheir associated wakeup signal (WUS), according to aspects of thedisclosure.

FIG. 7 illustrates a comparison between a first WUS that instructs a UEto skip the next DRX occasion and a second WUS that does not instruct aUE to skip the next DRX occasion, according to aspects of thedisclosure.

FIG. 8 illustrates an example configuration of a WUS monitoringoccasion, according to aspects of the disclosure.

FIG. 9 illustrates an example DCI format for WUS, according to aspectsof the disclosure.

FIG. 10 illustrates an example method of wireless communication,according to aspects of the disclosure.

DETAILED DESCRIPTION

Aspects of the disclosure are provided in the following description andrelated drawings directed to various examples provided for illustrationpurposes. Alternate aspects may be devised without departing from thescope of the disclosure. Additionally, well-known elements of thedisclosure will not be described in detail or will be omitted so as notto obscure the relevant details of the disclosure.

The words “exemplary” and/or “example” are used herein to mean “servingas an example, instance, or illustration.” Any aspect described hereinas “exemplary” and/or “example” is not necessarily to be construed aspreferred or advantageous over other aspects. Likewise, the term“aspects of the disclosure” does not require that all aspects of thedisclosure include the discussed feature, advantage or mode ofoperation.

Those of skill in the art will appreciate that the information andsignals described below may be represented using any of a variety ofdifferent technologies and techniques. For example, data, instructions,commands, information, signals, bits, symbols, and chips that may bereferenced throughout the description below may be represented byvoltages, currents, electromagnetic waves, magnetic fields or particles,optical fields or particles, or any combination thereof, depending inpart on the particular application, in part on the desired design, inpart on the corresponding technology, etc.

Further, many aspects are described in terms of sequences of actions tobe performed by, for example, elements of a computing device. It will berecognized that various actions described herein can be performed byspecific circuits (e.g., application specific integrated circuits(ASICs)), by program instructions being executed by one or moreprocessors, or by a combination of both. Additionally, the sequence(s)of actions described herein can be considered to be embodied entirelywithin any form of non-transitory computer-readable storage mediumhaving stored therein a corresponding set of computer instructions that,upon execution, would cause or instruct an associated processor of adevice to perform the functionality described herein. Thus, the variousaspects of the disclosure may be embodied in a number of differentforms, all of which have been contemplated to be within the scope of theclaimed subject matter. In addition, for each of the aspects describedherein, the corresponding form of any such aspects may be describedherein as, for example, “logic configured to” perform the describedaction.

As used herein, the terms “user equipment” (UE) and “base station” arenot intended to be specific or otherwise limited to any particular radioaccess technology (RAT), unless otherwise noted. In general, a UE may beany wireless communication device (e.g., a mobile phone, router, tabletcomputer, laptop computer, consumer asset locating device, wearable(e.g., smartwatch, glasses, augmented reality (AR)/virtual reality (VR)headset, etc.), vehicle (e.g., automobile, motorcycle, bicycle, etc.),Internet of Things (IoT) device, etc.) used by a user to communicateover a wireless communications network. A UE may be mobile or may (e.g.,at certain times) be stationary, and may communicate with a radio accessnetwork (RAN). As used herein, the term “UE” may be referred tointerchangeably as an “access terminal” or “AT,” a “client device,” a“wireless device,” a “subscriber device,” a “subscriber terminal,” a“subscriber station,” a “user terminal” or “UT,” a “mobile device,” a“mobile terminal,” a “mobile station,” or variations thereof. Generally,UEs can communicate with a core network via a RAN, and through the corenetwork the UEs can be connected with external networks such as theInternet and with other UEs. Of course, other mechanisms of connectingto the core network and/or the Internet are also possible for the UEs,such as over wired access networks, wireless local area network (WLAN)networks (e.g., based on the Institute of Electrical and ElectronicsEngineers (IEEE) 802.11 specification, etc.) and so on.

A base station may operate according to one of several RATs incommunication with UEs depending on the network in which it is deployed,and may be alternatively referred to as an access point (AP), a networknode, a NodeB, an evolved NodeB (eNB), a next generation eNB (ng-eNB), aNew Radio (NR) Node B (also referred to as a gNB or gNodeB), etc. A basestation may be used primarily to support wireless access by UEs,including supporting data, voice, and/or signaling connections for thesupported UEs. In some systems a base station may provide purely edgenode signaling functions while in other systems it may provideadditional control and/or network management functions. A communicationlink through which UEs can send signals to a base station is called anuplink (UL) channel (e.g., a reverse traffic channel, a reverse controlchannel, an access channel, etc.). A communication link through whichthe base station can send signals to UEs is called a downlink (DL) orforward link channel (e.g., a paging channel, a control channel, abroadcast channel, a forward traffic channel, etc.). As used herein theterm traffic channel (TCH) can refer to either an uplink/reverse ordownlink/forward traffic channel.

The term “base station” may refer to a single physicaltransmission-reception point (TRP) or to multiple physical TRPs that mayor may not be co-located. For example, where the term “base station”refers to a single physical TRP, the physical TRP may be an antenna ofthe base station corresponding to a cell (or several cell sectors) ofthe base station. Where the term “base station” refers to multipleco-located physical TRPs, the physical TRPs may be an array of antennas(e.g., as in a multiple-input multiple-output (MIMO) system or where thebase station employs beamforming) of the base station. Where the term“base station” refers to multiple non-co-located physical TRPs, thephysical TRPs may be a distributed antenna system (DAS) (a network ofspatially separated antennas connected to a common source via atransport medium) or a remote radio head (RRH) (a remote base stationconnected to a serving base station). Alternatively, the non-co-locatedphysical TRPs may be the serving base station receiving the measurementreport from the UE and a neighbor base station whose reference radiofrequency (RF) signals the UE is measuring. Because a TRP is the pointfrom which a base station transmits and receives wireless signals, asused herein, references to transmission from or reception at a basestation are to be understood as referring to a particular TRP of thebase station.

In some implementations that support positioning of UEs, a base stationmay not support wireless access by UEs (e.g., may not support data,voice, and/or signaling connections for UEs), but may instead transmitreference signals to UEs to be measured by the UEs, and/or may receiveand measure signals transmitted by the UEs. Such a base station may bereferred to as a positioning beacon (e.g., when transmitting signals toUEs) and/or as a location measurement unit (e.g., when receiving andmeasuring signals from UEs).

An “RF signal” comprises an electromagnetic wave of a given frequencythat transports information through the space between a transmitter anda receiver. As used herein, a transmitter may transmit a single “RFsignal” or multiple “RF signals” to a receiver. However, the receivermay receive multiple “RF signals” corresponding to each transmitted RFsignal due to the propagation characteristics of RF signals throughmultipath channels. The same transmitted RF signal on different pathsbetween the transmitter and receiver may be referred to as a “multipath”RF signal. As used herein, an RF signal may also be referred to as a“wireless signal” or simply a “signal” where it is clear from thecontext that the term “signal” refers to a wireless signal or an RFsignal.

FIG. 1 illustrates an example wireless communications system 100,according to aspects of the disclosure. The wireless communicationssystem 100 (which may also be referred to as a wireless wide areanetwork (WWAN)) may include various base stations 102 (labeled “BS”) andvarious UEs 104. The base stations 102 may include macro cell basestations (high power cellular base stations) and/or small cell basestations (low power cellular base stations). In an aspect, the macrocell base stations may include eNBs and/or ng-eNBs where the wirelesscommunications system 100 corresponds to an LTE network, or gNBs wherethe wireless communications system 100 corresponds to a NR network, or acombination of both, and the small cell base stations may includefemtocells, picocells, microcells, etc.

The base stations 102 may collectively form a RAN and interface with acore network 170 (e.g., an evolved packet core (EPC) or a 5G core (5GC))through backhaul links 122, and through the core network 170 to one ormore location servers 172 (e.g., a location management function (LMF) ora secure user plane location (SUPL) location platform (SLP)). Thelocation server(s) 172 may be part of core network 170 or may beexternal to core network 170. In addition to other functions, the basestations 102 may perform functions that relate to one or more oftransferring user data, radio channel ciphering and deciphering,integrity protection, header compression, mobility control functions(e.g., handover, dual connectivity), inter-cell interferencecoordination, connection setup and release, load balancing, distributionfor non-access stratum (NAS) messages, NAS node selection,synchronization, RAN sharing, multimedia broadcast multicast service(MBMS), subscriber and equipment trace, RAN information management(RIM), paging, positioning, and delivery of warning messages. The basestations 102 may communicate with each other directly or indirectly(e.g., through the EPC/5GC) over backhaul links 134, which may be wiredor wireless.

The base stations 102 may wirelessly communicate with the UEs 104. Eachof the base stations 102 may provide communication coverage for arespective geographic coverage area 110. In an aspect, one or more cellsmay be supported by a base station 102 in each geographic coverage area110. A “cell” is a logical communication entity used for communicationwith a base station (e.g., over some frequency resource, referred to asa carrier frequency, component carrier, carrier, band, or the like), andmay be associated with an identifier (e.g., a physical cell identifier(PCI), an enhanced cell identifier (ECI), a virtual cell identifier(VCI), a cell global identifier (CGI), etc.) for distinguishing cellsoperating via the same or a different carrier frequency. In some cases,different cells may be configured according to different protocol types(e.g., machine-type communication (MTC), narrowband IoT (NB-IoT),enhanced mobile broadband (eMBB), or others) that may provide access fordifferent types of UEs. Because a cell is supported by a specific basestation, the term “cell” may refer to either or both of the logicalcommunication entity and the base station that supports it, depending onthe context. In addition, because a TRP is typically the physicaltransmission point of a cell, the terms “cell” and “TRP” may be usedinterchangeably. In some cases, the term “cell” may also refer to ageographic coverage area of a base station (e.g., a sector), insofar asa carrier frequency can be detected and used for communication withinsome portion of geographic coverage areas 110.

While neighboring macro cell base station 102 geographic coverage areas110 may partially overlap (e.g., in a handover region), some of thegeographic coverage areas 110 may be substantially overlapped by alarger geographic coverage area 110. For example, a small cell basestation 102′ (labeled “SC” for “small cell”) may have a geographiccoverage area 110′ that substantially overlaps with the geographiccoverage area 110 of one or more macro cell base stations 102. A networkthat includes both small cell and macro cell base stations may be knownas a heterogeneous network. A heterogeneous network may also includehome eNBs (HeNBs), which may provide service to a restricted group knownas a closed subscriber group (CSG).

The communication links 120 between the base stations 102 and the UEs104 may include uplink (also referred to as reverse link) transmissionsfrom a UE 104 to a base station 102 and/or downlink (DL) (also referredto as forward link) transmissions from a base station 102 to a UE 104.The communication links 120 may use MIMO antenna technology, includingspatial multiplexing, beamforming, and/or transmit diversity. Thecommunication links 120 may be through one or more carrier frequencies.Allocation of carriers may be asymmetric with respect to downlink anduplink (e.g., more or less carriers may be allocated for downlink thanfor uplink).

The wireless communications system 100 may further include a wirelesslocal area network (WLAN) access point (AP) 150 in communication withWLAN stations (STAs) 152 via communication links 154 in an unlicensedfrequency spectrum (e.g., 5 GHz). When communicating in an unlicensedfrequency spectrum, the WLAN STAs 152 and/or the WLAN AP 150 may performa clear channel assessment (CCA) or listen before talk (LBT) procedureprior to communicating in order to determine whether the channel isavailable.

The small cell base station 102′ may operate in a licensed and/or anunlicensed frequency spectrum. When operating in an unlicensed frequencyspectrum, the small cell base station 102′ may employ LTE or NRtechnology and use the same 5 GHz unlicensed frequency spectrum as usedby the WLAN AP 150. The small cell base station 102′, employing LTE/5Gin an unlicensed frequency spectrum, may boost coverage to and/orincrease capacity of the access network. NR in unlicensed spectrum maybe referred to as NR-U. LTE in an unlicensed spectrum may be referred toas LTE-U, licensed assisted access (LAA), or MulteFire.

The wireless communications system 100 may further include a millimeterwave (mmW) base station 180 that may operate in mmW frequencies and/ornear mmW frequencies in communication with a UE 182. Extremely highfrequency (EHF) is part of the RF in the electromagnetic spectrum. EHFhas a range of 30 GHz to 300 GHz and a wavelength between 1 millimeterand 10 millimeters. Radio waves in this band may be referred to as amillimeter wave. Near mmW may extend down to a frequency of 3 GHz with awavelength of 100 millimeters. The super high frequency (SHF) bandextends between 3 GHz and 30 GHz, also referred to as centimeter wave.Communications using the mmW/near mmW radio frequency band have highpath loss and a relatively short range. The mmW base station 180 and theUE 182 may utilize beamforming (transmit and/or receive) over a mmWcommunication link 184 to compensate for the extremely high path lossand short range. Further, it will be appreciated that in alternativeconfigurations, one or more base stations 102 may also transmit usingmmW or near mmW and beamforming. Accordingly, it will be appreciatedthat the foregoing illustrations are merely examples and should not beconstrued to limit the various aspects disclosed herein.

Transmit beamforming is a technique for focusing an RF signal in aspecific direction. Traditionally, when a network node (e.g., a basestation) broadcasts an RF signal, it broadcasts the signal in alldirections (omni-directionally). With transmit beamforming, the networknode determines where a given target device (e.g., a UE) is located(relative to the transmitting network node) and projects a strongerdownlink RF signal in that specific direction, thereby providing afaster (in terms of data rate) and stronger RF signal for the receivingdevice(s). To change the directionality of the RF signal whentransmitting, a network node can control the phase and relativeamplitude of the RF signal at each of the one or more transmitters thatare broadcasting the RF signal. For example, a network node may use anarray of antennas (referred to as a “phased array” or an “antennaarray”) that creates a beam of RF waves that can be “steered” to pointin different directions, without actually moving the antennas.Specifically, the RF current from the transmitter is fed to theindividual antennas with the correct phase relationship so that theradio waves from the separate antennas add together to increase theradiation in a desired direction, while cancelling to suppress radiationin undesired directions.

Transmit beams may be quasi-co-located, meaning that they appear to thereceiver (e.g., a UE) as having the same parameters, regardless ofwhether or not the transmitting antennas of the network node themselvesare physically co-located. In NR, there are four types ofquasi-co-location (QCL) relations. Specifically, a QCL relation of agiven type means that certain parameters about a second reference RFsignal on a second beam can be derived from information about a sourcereference RF signal on a source beam. Thus, if the source reference RFsignal is QCL Type A, the receiver can use the source reference RFsignal to estimate the Doppler shift, Doppler spread, average delay, anddelay spread of a second reference RF signal transmitted on the samechannel. If the source reference RF signal is QCL Type B, the receivercan use the source reference RF signal to estimate the Doppler shift andDoppler spread of a second reference RF signal transmitted on the samechannel. If the source reference RF signal is QCL Type C, the receivercan use the source reference RF signal to estimate the Doppler shift andaverage delay of a second reference RF signal transmitted on the samechannel. If the source reference RF signal is QCL Type D, the receivercan use the source reference RF signal to estimate the spatial receiveparameter of a second reference RF signal transmitted on the samechannel.

In receive beamforming, the receiver uses a receive beam to amplify RFsignals detected on a given channel. For example, the receiver canincrease the gain setting and/or adjust the phase setting of an array ofantennas in a particular direction to amplify (e.g., to increase thegain level of) the RF signals received from that direction. Thus, when areceiver is said to beamform in a certain direction, it means the beamgain in that direction is high relative to the beam gain along otherdirections, or the beam gain in that direction is the highest comparedto the beam gain in that direction of all other receive beams availableto the receiver. This results in a stronger received signal strength(e.g., reference signal received power (RSRP), reference signal receivedquality (RSRQ), signal-to-interference-plus-noise ratio (SINR), etc.) ofthe RF signals received from that direction.

Transmit and receive beams may be spatially related. A spatial relationmeans that parameters for a second beam (e.g., a transmit or receivebeam) for a second reference signal can be derived from informationabout a first beam (e.g., a receive beam or a transmit beam) for a firstreference signal. For example, a UE may use a particular receive beam toreceive a reference downlink reference signal (e.g., synchronizationsignal block (SSB)) from a base station. The UE can then form a transmitbeam for sending an uplink reference signal (e.g., sounding referencesignal (SRS)) to that base station based on the parameters of thereceive beam.

Note that a “downlink” beam may be either a transmit beam or a receivebeam, depending on the entity forming it. For example, if a base stationis forming the downlink beam to transmit a reference signal to a UE, thedownlink beam is a transmit beam. If the UE is forming the downlinkbeam, however, it is a receive beam to receive the downlink referencesignal. Similarly, an “uplink” beam may be either a transmit beam or areceive beam, depending on the entity forming it. For example, if a basestation is forming the uplink beam, it is an uplink receive beam, and ifa UE is forming the uplink beam, it is an uplink transmit beam.

In 5G, the frequency spectrum in which wireless nodes (e.g., basestations 102/180, UEs 104/182) operate is divided into multiplefrequency ranges, FR1 (from 450 to 6000 MHz), FR2 (from 24250 to 52600MHz), FR3 (above 52600 MHz), and FR4 (between FR1 and FR2). mmWfrequency bands generally include the FR2, FR3, and FR4 frequencyranges. As such, the terms “mmW” and “FR2” or “FR3” or “FR4” maygenerally be used interchangeably.

In a multi-carrier system, such as 5G, one of the carrier frequencies isreferred to as the “primary carrier” or “anchor carrier” or “primaryserving cell” or “PCell,” and the remaining carrier frequencies arereferred to as “secondary carriers” or “secondary serving cells” or“SCells.” In carrier aggregation, the anchor carrier is the carrieroperating on the primary frequency (e.g., FR1) utilized by a UE 104/182and the cell in which the UE 104/182 either performs the initial radioresource control (RRC) connection establishment procedure or initiatesthe RRC connection re-establishment procedure. The primary carriercarries all common and UE-specific control channels, and may be acarrier in a licensed frequency (however, this is not always the case).A secondary carrier is a carrier operating on a second frequency (e.g.,FR2) that may be configured once the RRC connection is establishedbetween the UE 104 and the anchor carrier and that may be used toprovide additional radio resources. In some cases, the secondary carriermay be a carrier in an unlicensed frequency. The secondary carrier maycontain only necessary signaling information and signals, for example,those that are UE-specific may not be present in the secondary carrier,since both primary uplink and downlink carriers are typicallyUE-specific. This means that different UEs 104/182 in a cell may havedifferent downlink primary carriers. The same is true for the uplinkprimary carriers. The network is able to change the primary carrier ofany UE 104/182 at any time. This is done, for example, to balance theload on different carriers. Because a “serving cell” (whether a PCell oran SCell) corresponds to a carrier frequency/component carrier overwhich some base station is communicating, the term “cell,” “servingcell,” “component carrier,” “carrier frequency,” and the like can beused interchangeably.

For example, still referring to FIG. 1 , one of the frequencies utilizedby the macro cell base stations 102 may be an anchor carrier (or“PCell”) and other frequencies utilized by the macro cell base stations102 and/or the mmW base station 180 may be secondary carriers(“SCells”). The simultaneous transmission and/or reception of multiplecarriers enables the UE 104/182 to significantly increase its datatransmission and/or reception rates. For example, two 20 MHz aggregatedcarriers in a multi-carrier system would theoretically lead to atwo-fold increase in data rate (i.e., 40 MHz), compared to that attainedby a single 20 MHz carrier.

The wireless communications system 100 may further include a UE 164 thatmay communicate with a macro cell base station 102 over a communicationlink 120 and/or the mmW base station 180 over a mmW communication link184. For example, the macro cell base station 102 may support a PCelland one or more SCells for the UE 164 and the mmW base station 180 maysupport one or more SCells for the UE 164.

In the example of FIG. 1 , one or more Earth orbiting satellitepositioning system (SPS) space vehicles (SVs) 112 (e.g., satellites) maybe used as an independent source of location information for any of theillustrated UEs (shown in FIG. 1 as a single UE 104 for simplicity). AUE 104 may include one or more dedicated SPS receivers specificallydesigned to receive SPS signals 124 for deriving geo locationinformation from the SVs 112. An SPS typically includes a system oftransmitters (e.g., SVs 112) positioned to enable receivers (e.g., UEs104) to determine their location on or above the Earth based, at leastin part, on signals (e.g., SPS signals 124) received from thetransmitters. Such a transmitter typically transmits a signal markedwith a repeating pseudo-random noise (PN) code of a set number of chips.While typically located in SVs 112, transmitters may sometimes belocated on ground-based control stations, base stations 102, and/orother UEs 104.

The use of SPS signals 124 can be augmented by various satellite-basedaugmentation systems (SBAS) that may be associated with or otherwiseenabled for use with one or more global and/or regional navigationsatellite systems. For example an SBAS may include an augmentationsystem(s) that provides integrity information, differential corrections,etc., such as the Wide Area Augmentation System (WAAS), the EuropeanGeostationary Navigation Overlay Service (EGNOS), the Multi-functionalSatellite Augmentation System (MSAS), the Global Positioning System(GPS) Aided Geo Augmented Navigation or GPS and Geo Augmented Navigationsystem (GAGAN), and/or the like. Thus, as used herein, an SPS mayinclude any combination of one or more global and/or regional navigationsatellite systems and/or augmentation systems, and SPS signals 124 mayinclude SPS, SPS-like, and/or other signals associated with such one ormore SPS.

The wireless communications system 100 may further include one or moreUEs, such as UE 190, that connects indirectly to one or morecommunication networks via one or more device-to-device (D2D)peer-to-peer (P2P) links (referred to as “sidelinks”). In the example ofFIG. 1 , UE 190 has a D2D P2P link 192 with one of the UEs 104 connectedto one of the base stations 102 (e.g., through which UE 190 mayindirectly obtain cellular connectivity) and a D2D P2P link 194 withWLAN STA 152 connected to the WLAN AP 150 (through which UE 190 mayindirectly obtain WLAN-based Internet connectivity). In an example, theD2D P2P links 192 and 194 may be supported with any well-known D2D RAT,such as LTE Direct (LTE-D), WiFi Direct (WiFi-D), Bluetooth®, and so on.

FIG. 2A illustrates an example wireless network structure 200. Forexample, a 5GC 210 (also referred to as a Next Generation Core (NGC))can be viewed functionally as control plane (C-plane) functions 214(e.g., UE registration, authentication, network access, gatewayselection, etc.) and user plane (U-plane) functions 212, (e.g., UEgateway function, access to data networks, IP routing, etc.) whichoperate cooperatively to form the core network. User plane interface(NG-U) 213 and control plane interface (NG-C) 215 connect the gNB 222 tothe 5GC 210 and specifically to the user plane functions 212 and controlplane functions 214, respectively. In an additional configuration, anng-eNB 224 may also be connected to the 5GC 210 via NG-C 215 to thecontrol plane functions 214 and NG-U 213 to user plane functions 212.Further, ng-eNB 224 may directly communicate with gNB 222 via a backhaulconnection 223. In some configurations, a Next Generation RAN (NG-RAN)220 may have one or more gNBs 222, while other configurations includeone or more of both ng-eNBs 224 and gNBs 222. Either (or both) gNB 222or ng-eNB 224 may communicate with one or more UEs 204 (e.g., any of theUEs described herein).

Another optional aspect may include a location server 230, which may bein communication with the 5GC 210 to provide location assistance forUE(s) 204. The location server 230 can be implemented as a plurality ofseparate servers (e.g., physically separate servers, different softwaremodules on a single server, different software modules spread acrossmultiple physical servers, etc.), or alternately may each correspond toa single server. The location server 230 can be configured to supportone or more location services for UEs 204 that can connect to thelocation server 230 via the core network, 5GC 210, and/or via theInternet (not illustrated). Further, the location server 230 may beintegrated into a component of the core network, or alternatively may beexternal to the core network (e.g., a third party server, such as anoriginal equipment manufacturer (OEM) server or service server).

FIG. 2B illustrates another example wireless network structure 250. A5GC 260 (which may correspond to 5GC 210 in FIG. 2A) can be viewedfunctionally as control plane functions, provided by an access andmobility management function (AMF) 264, and user plane functions,provided by a user plane function (UPF) 262, which operate cooperativelyto form the core network (i.e., 5GC 260). The functions of the AMF 264include registration management, connection management, reachabilitymanagement, mobility management, lawful interception, transport forsession management (SM) messages between one or more UEs 204 (e.g., anyof the UEs described herein) and a session management function (SMF)266, transparent proxy services for routing SM messages, accessauthentication and access authorization, transport for short messageservice (SMS) messages between the UE 204 and the short message servicefunction (SMSF) (not shown), and security anchor functionality (SEAF).The AMF 264 also interacts with an authentication server function (AUSF)(not shown) and the UE 204, and receives the intermediate key that wasestablished as a result of the UE 204 authentication process. In thecase of authentication based on a UMTS (universal mobiletelecommunications system) subscriber identity module (USIM), the AMF264 retrieves the security material from the AUSF. The functions of theAMF 264 also include security context management (SCM). The SCM receivesa key from the SEAF that it uses to derive access-network specific keys.The functionality of the AMF 264 also includes location servicesmanagement for regulatory services, transport for location servicesmessages between the UE 204 and a location management function (LMF) 270(which acts as a location server 230), transport for location servicesmessages between the NG-RAN 220 and the LMF 270, evolved packet system(EPS) bearer identifier allocation for interworking with the EPS, and UE204 mobility event notification. In addition, the AMF 264 also supportsfunctionalities for non-3GPP (Third Generation Partnership Project)access networks.

Functions of the UPF 262 include acting as an anchor point forintra-/inter-RAT mobility (when applicable), acting as an externalprotocol data unit (PDU) session point of interconnect to a data network(not shown), providing packet routing and forwarding, packet inspection,user plane policy rule enforcement (e.g., gating, redirection, trafficsteering), lawful interception (user plane collection), traffic usagereporting, quality of service (QoS) handling for the user plane (e.g.,uplink/downlink rate enforcement, reflective QoS marking in thedownlink), uplink traffic verification (service data flow (SDF) to QoSflow mapping), transport level packet marking in the uplink anddownlink, downlink packet buffering and downlink data notificationtriggering, and sending and forwarding of one or more “end markers” tothe source RAN node. The UPF 262 may also support transfer of locationservices messages over a user plane between the UE 204 and a locationserver, such as an SLP 272.

The functions of the SMF 266 include session management, UE Internetprotocol (IP) address allocation and management, selection and controlof user plane functions, configuration of traffic steering at the UPF262 to route traffic to the proper destination, control of part ofpolicy enforcement and QoS, and downlink data notification. Theinterface over which the SMF 266 communicates with the AMF 264 isreferred to as the N11 interface.

Another optional aspect may include an LMF 270, which may be incommunication with the 5GC 260 to provide location assistance for UEs204. The LMF 270 can be implemented as a plurality of separate servers(e.g., physically separate servers, different software modules on asingle server, different software modules spread across multiplephysical servers, etc.), or alternately may each correspond to a singleserver. The LMF 270 can be configured to support one or more locationservices for UEs 204 that can connect to the LMF 270 via the corenetwork, 5GC 260, and/or via the Internet (not illustrated). The SLP 272may support similar functions to the LMF 270, but whereas the LMF 270may communicate with the AMF 264, NG-RAN 220, and UEs 204 over a controlplane (e.g., using interfaces and protocols intended to convey signalingmessages and not voice or data), the SLP 272 may communicate with UEs204 and external clients (not shown in FIG. 2B) over a user plane (e.g.,using protocols intended to carry voice and/or data like thetransmission control protocol (TCP) and/or IP).

User plane interface 263 and control plane interface 265 connect the 5GC260, and specifically the UPF 262 and AMF 264, respectively, to one ormore gNBs 222 and/or ng-eNBs 224 in the NG-RAN 220. The interfacebetween gNB(s) 222 and/or ng-eNB(s) 224 and the AMF 264 is referred toas the “N2” interface, and the interface between gNB(s) 222 and/orng-eNB(s) 224 and the UPF 262 is referred to as the “N3” interface. ThegNB(s) 222 and/or ng-eNB(s) 224 of the NG-RAN 220 may communicatedirectly with each other via backhaul connections 223, referred to asthe “Xn-C” interface. One or more of gNBs 222 and/or ng-eNBs 224 maycommunicate with one or more UEs 204 over a wireless interface, referredto as the “Uu” interface.

The functionality of a gNB 222 is divided between a gNB central unit(gNB-CU) 226 and one or more gNB distributed units (gNB-DUs) 228. Theinterface 232 between the gNB-CU 226 and the one or more gNB-DUs 228 isreferred to as the “F1” interface. A gNB-CU 226 is a logical node thatincludes the base station functions of transferring user data, mobilitycontrol, radio access network sharing, positioning, session management,and the like, except for those functions allocated exclusively to thegNB-DU(s) 228. More specifically, the gNB-CU 226 hosts the radioresource control (RRC), service data adaptation protocol (SDAP), andpacket data convergence protocol (PDCP) protocols of the gNB 222. AgNB-DU 228 is a logical node that hosts the radio link control (RLC),medium access control (MAC), and physical (PHY) layers of the gNB 222.Its operation is controlled by the gNB-CU 226. One gNB-DU 228 cansupport one or more cells, and one cell is supported by only one gNB-DU228. Thus, a UE 204 communicates with the gNB-CU 226 via the RRC, SDAP,and PDCP layers and with a gNB-DU 228 via the RLC, MAC, and PHY layers.

FIGS. 3A, 3B, and 3C illustrate several example components (representedby corresponding blocks) that may be incorporated into a UE 302 (whichmay correspond to any of the UEs described herein), a base station 304(which may correspond to any of the base stations described herein), anda network entity 306 (which may correspond to or embody any of thenetwork functions described herein, including the location server 230and the LMF 270, or alternatively may be independent from the NG-RAN 220and/or 5GC 210/260 infrastructure depicted in FIGS. 2A and 2B, such as aprivate network) to support the file transmission operations as taughtherein. It will be appreciated that these components may be implementedin different types of apparatuses in different implementations (e.g., inan ASIC, in a system-on-chip (SoC), etc.). The illustrated componentsmay also be incorporated into other apparatuses in a communicationsystem. For example, other apparatuses in a system may includecomponents similar to those described to provide similar functionality.Also, a given apparatus may contain one or more of the components. Forexample, an apparatus may include multiple transceiver components thatenable the apparatus to operate on multiple carriers and/or communicatevia different technologies.

The UE 302 and the base station 304 each include one or more wirelesswide area network (WWAN) transceivers 310 and 350, respectively,providing means for communicating (e.g., means for transmitting, meansfor receiving, means for measuring, means for tuning, means forrefraining from transmitting, etc.) via one or more wirelesscommunication networks (not shown), such as an NR network, an LTEnetwork, a GSM network, and/or the like. The WWAN transceivers 310 and350 may each be connected to one or more antennas 316 and 356,respectively, for communicating with other network nodes, such as otherUEs, access points, base stations (e.g., eNBs, gNBs), etc., via at leastone designated RAT (e.g., NR, LTE, GSM, etc.) over a wirelesscommunication medium of interest (e.g., some set of time/frequencyresources in a particular frequency spectrum). The WWAN transceivers 310and 350 may be variously configured for transmitting and encodingsignals 318 and 358 (e.g., messages, indications, information, and soon), respectively, and, conversely, for receiving and decoding signals318 and 358 (e.g., messages, indications, information, pilots, and soon), respectively, in accordance with the designated RAT. Specifically,the WWAN transceivers 310 and 350 include one or more transmitters 314and 354, respectively, for transmitting and encoding signals 318 and358, respectively, and one or more receivers 312 and 352, respectively,for receiving and decoding signals 318 and 358, respectively.

The UE 302 and the base station 304 each also include, at least in somecases, one or more short-range wireless transceivers 320 and 360,respectively. The short-range wireless transceivers 320 and 360 may beconnected to one or more antennas 326 and 366, respectively, and providemeans for communicating (e.g., means for transmitting, means forreceiving, means for measuring, means for tuning, means for refrainingfrom transmitting, etc.) with other network nodes, such as other UEs,access points, base stations, etc., via at least one designated RAT(e.g., WiFi, LTE-D, Bluetooth®, Zigbee®, Z-Wave®, PC5, dedicatedshort-range communications (DSRC), wireless access for vehicularenvironments (WAVE), near-field communication (NFC), etc.) over awireless communication medium of interest. The short-range wirelesstransceivers 320 and 360 may be variously configured for transmittingand encoding signals 328 and 368 (e.g., messages, indications,information, and so on), respectively, and, conversely, for receivingand decoding signals 328 and 368 (e.g., messages, indications,information, pilots, and so on), respectively, in accordance with thedesignated RAT. Specifically, the short-range wireless transceivers 320and 360 include one or more transmitters 324 and 364, respectively, fortransmitting and encoding signals 328 and 368, respectively, and one ormore receivers 322 and 362, respectively, for receiving and decodingsignals 328 and 368, respectively. As specific examples, the short-rangewireless transceivers 320 and 360 may be WiFi transceivers, Bluetooth®transceivers, Zigbee® and/or Z-Wave® transceivers, NFC transceivers, orvehicle-to-vehicle (V2V) and/or vehicle-to-everything (V2X)transceivers.

The UE 302 and the base station 304 also include, at least in somecases, satellite positioning systems (SPS) receivers 330 and 370. TheSPS receivers 330 and 370 may be connected to one or more antennas 336and 376, respectively, and may provide means for receiving and/ormeasuring SPS signals 338 and 378, respectively, such as globalpositioning system (GPS) signals, global navigation satellite system(GLONASS) signals, Galileo signals, Beidou signals, Indian RegionalNavigation Satellite System (NAVIC), Quasi-Zenith Satellite System(QZSS), etc. The SPS receivers 330 and 370 may comprise any suitablehardware and/or software for receiving and processing SPS signals 338and 378, respectively. The SPS receivers 330 and 370 request informationand operations as appropriate from the other systems, and performscalculations necessary to determine positions of the UE 302 and the basestation 304 using measurements obtained by any suitable SPS algorithm.

The base station 304 and the network entity 306 each include one or morenetwork transceivers 380 and 390, respectively, providing means forcommunicating (e.g., means for transmitting, means for receiving, etc.)with other network entities (e.g., other base stations 304, othernetwork entities 306). For example, the base station 304 may employ theone or more network transceivers 380 to communicate with other basestations 304 or network entities 306 over one or more wired or wirelessbackhaul links. As another example, the network entity 306 may employthe one or more network transceivers 390 to communicate with one or morebase station 304 over one or more wired or wireless backhaul links, orwith other network entities 306 over one or more wired or wireless corenetwork interfaces.

A transceiver may be configured to communicate over a wired or wirelesslink. A transceiver (whether a wired transceiver or a wirelesstransceiver) includes transmitter circuitry (e.g., transmitters 314,324, 354, 364) and receiver circuitry (e.g., receivers 312, 322, 352,362). A transceiver may be an integrated device (e.g., embodyingtransmitter circuitry and receiver circuitry in a single device) in someimplementations, may comprise separate transmitter circuitry andseparate receiver circuitry in some implementations, or may be embodiedin other ways in other implementations. The transmitter circuitry andreceiver circuitry of a wired transceiver (e.g., network transceivers380 and 390 in some implementations) may be coupled to one or more wirednetwork interface ports. Wireless transmitter circuitry (e.g.,transmitters 314, 324, 354, 364) may include or be coupled to aplurality of antennas (e.g., antennas 316, 326, 356, 366), such as anantenna array, that permits the respective apparatus (e.g., UE 302, basestation 304) to perform transmit “beamforming,” as described herein.Similarly, wireless receiver circuitry (e.g., receivers 312, 322, 352,362) may include or be coupled to a plurality of antennas (e.g.,antennas 316, 326, 356, 366), such as an antenna array, that permits therespective apparatus (e.g., UE 302, base station 304) to perform receivebeamforming, as described herein. In an aspect, the transmittercircuitry and receiver circuitry may share the same plurality ofantennas (e.g., antennas 316, 326, 356, 366), such that the respectiveapparatus can only receive or transmit at a given time, not both at thesame time. A wireless transceiver (e.g., WWAN transceivers 310 and 350,short-range wireless transceivers 320 and 360) may also include anetwork listen module (NLM) or the like for performing variousmeasurements.

As used herein, the various wireless transceivers (e.g., transceivers310, 320, 350, and 360, and network transceivers 380 and 390 in someimplementations) and wired transceivers (e.g., network transceivers 380and 390 in some implementations) may generally be characterized as “atransceiver,” “at least one transceiver,” or “one or more transceivers.”As such, whether a particular transceiver is a wired or wirelesstransceiver may be inferred from the type of communication performed.For example, backhaul communication between network devices or serverswill generally relate to signaling via a wired transceiver, whereaswireless communication between a UE (e.g., UE 302) and a base station(e.g., base station 304) will generally relate to signaling via awireless transceiver.

The UE 302, the base station 304, and the network entity 306 alsoinclude other components that may be used in conjunction with theoperations as disclosed herein. The UE 302, the base station 304, andthe network entity 306 include one or more processors 332, 384, and 394,respectively, for providing functionality relating to, for example,wireless communication, and for providing other processingfunctionality. The processors 332, 384, and 394 may therefore providemeans for processing, such as means for determining, means forcalculating, means for receiving, means for transmitting, means forindicating, etc. In an aspect, the processors 332, 384, and 394 mayinclude, for example, one or more general purpose processors, multi-coreprocessors, central processing units (CPUs), ASICs, digital signalprocessors (DSPs), field programmable gate arrays (FPGAs), otherprogrammable logic devices or processing circuitry, or variouscombinations thereof.

The UE 302, the base station 304, and the network entity 306 includememory circuitry implementing memories 340, 386, and 396 (e.g., eachincluding a memory device), respectively, for maintaining information(e.g., information indicative of reserved resources, thresholds,parameters, and so on). The memories 340, 386, and 396 may thereforeprovide means for storing, means for retrieving, means for maintaining,etc. In some cases, the UE 302, the base station 304, and the networkentity 306 may include positioning component 342, 388, and 398,respectively. The positioning component 342, 388, and 398 may behardware circuits that are part of or coupled to the processors 332,384, and 394, respectively, that, when executed, cause the UE 302, thebase station 304, and the network entity 306 to perform thefunctionality described herein. In other aspects, the positioningcomponent 342, 388, and 398 may be external to the processors 332, 384,and 394 (e.g., part of a modem processing system, integrated withanother processing system, etc.). Alternatively, the positioningcomponent 342, 388, and 398 may be memory modules stored in the memories340, 386, and 396, respectively, that, when executed by the processors332, 384, and 394 (or a modem processing system, another processingsystem, etc.), cause the UE 302, the base station 304, and the networkentity 306 to perform the functionality described herein. FIG. 3Aillustrates possible locations of the positioning component 342, whichmay be, for example, part of the one or more WWAN transceivers 310, thememory 340, the one or more processors 332, or any combination thereof,or may be a standalone component. FIG. 3B illustrates possible locationsof the positioning component 388, which may be, for example, part of theone or more WWAN transceivers 350, the memory 386, the one or moreprocessors 384, or any combination thereof, or may be a standalonecomponent. FIG. 3C illustrates possible locations of the positioningcomponent 398, which may be, for example, part of the one or morenetwork transceivers 390, the memory 396, the one or more processors394, or any combination thereof, or may be a standalone component.

The UE 302 may include one or more sensors 344 coupled to the one ormore processors 332 to provide means for sensing or detecting movementand/or orientation information that is independent of motion dataderived from signals received by the one or more WWAN transceivers 310,the one or more short-range wireless transceivers 320, and/or the SPSreceiver 330. By way of example, the sensor(s) 344 may include anaccelerometer (e.g., a micro-electrical mechanical systems (MEMS)device), a gyroscope, a geomagnetic sensor (e.g., a compass), analtimeter (e.g., a barometric pressure altimeter), and/or any other typeof movement detection sensor. Moreover, the sensor(s) 344 may include aplurality of different types of devices and combine their outputs inorder to provide motion information. For example, the sensor(s) 344 mayuse a combination of a multi-axis accelerometer and orientation sensorsto provide the ability to compute positions in two-dimensional (2D)and/or three-dimensional (3D) coordinate systems.

In addition, the UE 302 includes a user interface 346 providing meansfor providing indications (e.g., audible and/or visual indications) to auser and/or for receiving user input (e.g., upon user actuation of asensing device such a keypad, a touch screen, a microphone, and so on).Although not shown, the base station 304 and the network entity 306 mayalso include user interfaces.

Referring to the one or more processors 384 in more detail, in thedownlink, IP packets from the network entity 306 may be provided to theprocessor 384. The one or more processors 384 may implementfunctionality for an RRC layer, a packet data convergence protocol(PDCP) layer, a radio link control (RLC) layer, and a medium accesscontrol (MAC) layer. The one or more processors 384 may provide RRClayer functionality associated with broadcasting of system information(e.g., master information block (MIB), system information blocks(SIBs)), RRC connection control (e.g., RRC connection paging, RRCconnection establishment, RRC connection modification, and RRCconnection release), inter-RAT mobility, and measurement configurationfor UE measurement reporting; PDCP layer functionality associated withheader compression/decompression, security (ciphering, deciphering,integrity protection, integrity verification), and handover supportfunctions; RLC layer functionality associated with the transfer of upperlayer PDUs, error correction through automatic repeat request (ARQ),concatenation, segmentation, and reassembly of RLC service data units(SDUs), re-segmentation of RLC data PDUs, and reordering of RLC dataPDUs; and MAC layer functionality associated with mapping betweenlogical channels and transport channels, scheduling informationreporting, error correction, priority handling, and logical channelprioritization.

The transmitter 354 and the receiver 352 may implement Layer-1 (L1)functionality associated with various signal processing functions.Layer-1, which includes a physical (PHY) layer, may include errordetection on the transport channels, forward error correction (FEC)coding/decoding of the transport channels, interleaving, rate matching,mapping onto physical channels, modulation/demodulation of physicalchannels, and MIMO antenna processing. The transmitter 354 handlesmapping to signal constellations based on various modulation schemes(e.g., binary phase-shift keying (BPSK), quadrature phase-shift keying(QPSK), M-phase-shift keying (M-PSK), M-quadrature amplitude modulation(M-QAM)). The coded and modulated symbols may then be split intoparallel streams. Each stream may then be mapped to an orthogonalfrequency division multiplexing (OFDM) subcarrier, multiplexed with areference signal (e.g., pilot) in the time and/or frequency domain, andthen combined together using an inverse fast Fourier transform (IFFT) toproduce a physical channel carrying a time domain OFDM symbol stream.The OFDM symbol stream is spatially precoded to produce multiple spatialstreams. Channel estimates from a channel estimator may be used todetermine the coding and modulation scheme, as well as for spatialprocessing. The channel estimate may be derived from a reference signaland/or channel condition feedback transmitted by the UE 302. Eachspatial stream may then be provided to one or more different antennas356. The transmitter 354 may modulate an RF carrier with a respectivespatial stream for transmission.

At the UE 302, the receiver 312 receives a signal through its respectiveantenna(s) 316.

The receiver 312 recovers information modulated onto an RF carrier andprovides the information to the one or more processors 332. Thetransmitter 314 and the receiver 312 implement Layer-1 functionalityassociated with various signal processing functions. The receiver 312may perform spatial processing on the information to recover any spatialstreams destined for the UE 302. If multiple spatial streams aredestined for the UE 302, they may be combined by the receiver 312 into asingle OFDM symbol stream. The receiver 312 then converts the OFDMsymbol stream from the time-domain to the frequency domain using a fastFourier transform (FFT). The frequency domain signal comprises aseparate OFDM symbol stream for each subcarrier of the OFDM signal. Thesymbols on each subcarrier, and the reference signal, are recovered anddemodulated by determining the most likely signal constellation pointstransmitted by the base station 304. These soft decisions may be basedon channel estimates computed by a channel estimator. The soft decisionsare then decoded and de-interleaved to recover the data and controlsignals that were originally transmitted by the base station 304 on thephysical channel. The data and control signals are then provided to theone or more processors 332, which implements Layer-3 (L3) and Layer-2(L2) functionality.

In the uplink, the one or more processors 332 provides demultiplexingbetween transport and logical channels, packet reassembly, deciphering,header decompression, and control signal processing to recover IPpackets from the core network. The one or more processors 332 are alsoresponsible for error detection.

Similar to the functionality described in connection with the downlinktransmission by the base station 304, the one or more processors 332provides RRC layer functionality associated with system information(e.g., MIB, SIBs) acquisition, RRC connections, and measurementreporting; PDCP layer functionality associated with headercompression/decompression, and security (ciphering, deciphering,integrity protection, integrity verification); RLC layer functionalityassociated with the transfer of upper layer PDUs, error correctionthrough ARQ, concatenation, segmentation, and reassembly of RLC SDUs,re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; andMAC layer functionality associated with mapping between logical channelsand transport channels, multiplexing of MAC SDUs onto transport blocks(TBs), demultiplexing of MAC SDUs from TBs, scheduling informationreporting, error correction through hybrid automatic repeat request(HARD), priority handling, and logical channel prioritization.

Channel estimates derived by the channel estimator from a referencesignal or feedback transmitted by the base station 304 may be used bythe transmitter 314 to select the appropriate coding and modulationschemes, and to facilitate spatial processing. The spatial streamsgenerated by the transmitter 314 may be provided to different antenna(s)316. The transmitter 314 may modulate an RF carrier with a respectivespatial stream for transmission.

The uplink transmission is processed at the base station 304 in a mannersimilar to that described in connection with the receiver function atthe UE 302. The receiver 352 receives a signal through its respectiveantenna(s) 356. The receiver 352 recovers information modulated onto anRF carrier and provides the information to the one or more processors384.

In the uplink, the one or more processors 384 provides demultiplexingbetween transport and logical channels, packet reassembly, deciphering,header decompression, control signal processing to recover IP packetsfrom the UE 302. IP packets from the one or more processors 384 may beprovided to the core network. The one or more processors 384 are alsoresponsible for error detection.

For convenience, the UE 302, the base station 304, and/or the networkentity 306 are shown in FIGS. 3A, 3B, and 3C as including variouscomponents that may be configured according to the various examplesdescribed herein. It will be appreciated, however, that the illustratedcomponents may have different functionality in different designs.

The various components of the UE 302, the base station 304, and thenetwork entity 306 may communicate with each other over data buses 334,382, and 392, respectively. In an aspect, the data buses 334, 382, and392 may form, or be part of, a communication interface of the UE 302,the base station 304, and the network entity 306, respectively. Forexample, where different logical entities are embodied in the samedevice (e.g., gNB and location server functionality incorporated intothe same base station 304), the data buses 334, 382, and 392 may providecommunication between them.

The components of FIGS. 3A, 3B, and 3C may be implemented in variousways. In some implementations, the components of FIGS. 3A, 3B, and 3Cmay be implemented in one or more circuits such as, for example, one ormore processors and/or one or more ASICs (which may include one or moreprocessors). Here, each circuit may use and/or incorporate at least onememory component for storing information or executable code used by thecircuit to provide this functionality. For example, some or all of thefunctionality represented by blocks 310 to 346 may be implemented byprocessor and memory component(s) of the UE 302 (e.g., by execution ofappropriate code and/or by appropriate configuration of processorcomponents). Similarly, some or all of the functionality represented byblocks 350 to 388 may be implemented by processor and memorycomponent(s) of the base station 304 (e.g., by execution of appropriatecode and/or by appropriate configuration of processor components). Also,some or all of the functionality represented by blocks 390 to 398 may beimplemented by processor and memory component(s) of the network entity306 (e.g., by execution of appropriate code and/or by appropriateconfiguration of processor components). For simplicity, variousoperations, acts, and/or functions are described herein as beingperformed “by a UE,” “by a base station,” “by a network entity,” etc.However, as will be appreciated, such operations, acts, and/or functionsmay actually be performed by specific components or combinations ofcomponents of the UE 302, base station 304, network entity 306, etc.,such as the processors 332, 384, 394, the transceivers 310, 320, 350,and 360, the memories 340, 386, and 396, the positioning component 342,388, and 398, etc.

In some designs, the network entity 306 may be implemented as a corenetwork component. In other designs, the network entity 306 may bedistinct from a network operator or operation of the cellular networkinfrastructure (e.g., NG RAN 220 and/or 5GC 210/260). For example, thenetwork entity 306 may be a component of a private network that may beconfigured to communicate with the UE 302 via the base station 304 orindependently from the base station 304 (e.g., over a non-cellularcommunication link, such as WiFi).

Various frame structures may be used to support downlink and uplinktransmissions between network nodes (e.g., base stations and UEs). FIG.4A is a diagram 400 illustrating an example of a downlink framestructure, according to aspects of the disclosure. FIG. 4B is a diagram430 illustrating an example of channels within the downlink framestructure, according to aspects of the disclosure. FIG. 4C is a diagram450 illustrating an example of an uplink frame structure, according toaspects of the disclosure. FIG. 4D is a diagram 480 illustrating anexample of channels within an uplink frame structure, according toaspects of the disclosure. Other wireless communications technologiesmay have different frame structures and/or different channels.

LTE, and in some cases NR, utilizes OFDM on the downlink andsingle-carrier frequency division multiplexing (SC-FDM) on the uplink.Unlike LTE, however, NR has an option to use OFDM on the uplink as well.OFDM and SC-FDM partition the system bandwidth into multiple (K)orthogonal subcarriers, which are also commonly referred to as tones,bins, etc. Each subcarrier may be modulated with data. In general,modulation symbols are sent in the frequency domain with OFDM and in thetime domain with SC-FDM. The spacing between adjacent subcarriers may befixed, and the total number of subcarriers (K) may be dependent on thesystem bandwidth. For example, the spacing of the subcarriers may be 15kilohertz (kHz) and the minimum resource allocation (resource block) maybe 12 subcarriers (or 180 kHz). Consequently, the nominal FFT size maybe equal to 128, 256, 512, 1024, or 2048 for system bandwidth of 1.25,2.5, 5, 10, or 20 megahertz (MHz), respectively. The system bandwidthmay also be partitioned into subbands. For example, a subband may cover1.08 MHz (i.e., 6 resource blocks), and there may be 1, 2, 4, 8, or 16subbands for system bandwidth of 1.25, 2.5, 5, 10, or 20 MHz,respectively.

LTE supports a single numerology (subcarrier spacing (SCS), symbollength, etc.). In contrast, NR may support multiple numerologies (μ),for example, subcarrier spacings of 15 kHz (μ=0), 30 kHz (μ=1), 60 kHz(μ=2), 120 kHz (μ=3), and 240 kHz (μ=4) or greater may be available. Ineach subcarrier spacing, there are 14 symbols per slot. For 15 kHz SCS(μ=0), there is one slot per subframe, 10 slots per frame, the slotduration is 1 millisecond (ms), the symbol duration is 66.7 microseconds(μs), and the maximum nominal system bandwidth (in MHz) with a 4K FFTsize is 50. For 30 kHz SCS (μ=1), there are two slots per subframe, 20slots per frame, the slot duration is 0.5 ms, the symbol duration is33.3 μs, and the maximum nominal system bandwidth (in MHz) with a 4K FFTsize is 100. For 60 kHz SCS (μ=2), there are four slots per subframe, 40slots per frame, the slot duration is 0.25 ms, the symbol duration is16.7 μs, and the maximum nominal system bandwidth (in MHz) with a 4K FFTsize is 200. For 120 kHz SCS (μ=3), there are eight slots per subframe,80 slots per frame, the slot duration is 0.125 ms, the symbol durationis 8.33 μs, and the maximum nominal system bandwidth (in MHz) with a 4KFFT size is 400. For 240 kHz SCS (μ=4), there are 16 slots per subframe,160 slots per frame, the slot duration is 0.0625 ms, the symbol durationis 4.17 μs, and the maximum nominal system bandwidth (in MHz) with a 4KFFT size is 800.

In the example of FIGS. 4A to 4D, a numerology of 15 kHz is used. Thus,in the time domain, a 10 ms frame is divided into 10 equally sizedsubframes of 1 ms each, and each subframe includes one time slot. InFIGS. 4A to 4D, time is represented horizontally (on the X axis) withtime increasing from left to right, while frequency is representedvertically (on the Y axis) with frequency increasing (or decreasing)from bottom to top.

A resource grid may be used to represent time slots, each time slotincluding one or more time-concurrent resource blocks (RBs) (alsoreferred to as physical RBs (PRBs)) in the frequency domain. Theresource grid is further divided into multiple resource elements (REs).An RE may correspond to one symbol length in the time domain and onesubcarrier in the frequency domain. In the numerology of FIGS. 4A to 4D,for a normal cyclic prefix, an RB may contain 12 consecutive subcarriersin the frequency domain and seven consecutive symbols in the timedomain, for a total of 84 REs. For an extended cyclic prefix, an RB maycontain 12 consecutive subcarriers in the frequency domain and sixconsecutive symbols in the time domain, for a total of 72 REs. Thenumber of bits carried by each RE depends on the modulation scheme.

Some of the REs carry downlink reference (pilot) signals (DL-RS). TheDL-RS may include positioning reference signals (PRS), trackingreference signals (TRS), phase tracking reference signals (TRS),cell-specific reference signals (CRS), channel state informationreference signals (CSI-RS), demodulation reference signals (DMRS),primary synchronization signals (PSS), secondary synchronization signals(SSS), synchronization signal blocks (SSBs), etc. FIG. 4A illustratesexample locations of REs carrying PRS (labeled “R”).

A collection of resource elements (REs) that are used for transmissionof PRS is referred to as a “PRS resource.” The collection of resourceelements can span multiple PRBs in the frequency domain and ‘N’ (such as1 or more) consecutive symbol(s) within a slot in the time domain. In agiven OFDM symbol in the time domain, a PRS resource occupiesconsecutive PRBs in the frequency domain.

The transmission of a PRS resource within a given PRB has a particularcomb size (also referred to as the “comb density”). A comb size ‘N’represents the subcarrier spacing (or frequency/tone spacing) withineach symbol of a PRS resource configuration. Specifically, for a combsize ‘N,’ PRS are transmitted in every Nth subcarrier of a symbol of aPRB. For example, for comb-4, for each symbol of the PRS resourceconfiguration, REs corresponding to every fourth subcarrier (such assubcarriers 0, 4, 8) are used to transmit PRS of the PRS resource.Currently, comb sizes of comb-2, comb-4, comb-6, and comb-12 aresupported for DL-PRS. FIG. 4A illustrates an example PRS resourceconfiguration for comb-6 (which spans six symbols). That is, thelocations of the shaded REs (labeled “R”) indicate a comb-6 PRS resourceconfiguration.

Currently, a DL-PRS resource may span 2, 4, 6, or 12 consecutive symbolswithin a slot with a fully frequency-domain staggered pattern. A DL-PRSresource can be configured in any higher layer configured downlink orflexible (FL) symbol of a slot. There may be a constant energy perresource element (EPRE) for all REs of a given DL-PRS resource. Thefollowing are the frequency offsets from symbol to symbol for comb sizes2, 4, 6, and 12 over 2, 4, 6, and 12 symbols. 2-symbol comb-2: {0, 1};4-symbol comb-2: {0, 1, 0, 1}; 6-symbol comb-2: {0, 1, 0, 1, 0, 1};12-symbol comb-2: {0, 1, 0, 1, 0, 1, 0, 1, 0, 1, 0, 1}; 4-symbol comb-4:{0, 2, 1, 3}; 12-symbol comb-4: {0, 2, 1, 3, 0, 2, 1, 3, 0, 2, 1, 3};6-symbol comb-6: {0, 3, 1, 4, 2, 5}; 12-symbol comb-6: {0, 3, 1, 4, 2,5, 0, 3, 1, 4, 2, 5}; and 12-symbol comb-12: {0, 6, 3, 9, 1, 7, 4, 10,2, 8, 5, 11}.

A “PRS resource set” is a set of PRS resources used for the transmissionof PRS signals, where each PRS resource has a PRS resource ID. Inaddition, the PRS resources in a PRS resource set are associated withthe same TRP. A PRS resource set is identified by a PRS resource set IDand is associated with a particular TRP (identified by a TRP ID). Inaddition, the PRS resources in a PRS resource set have the sameperiodicity, a common muting pattern configuration, and the samerepetition factor (such as “PRS-ResourceRepetitionFactor”) across slots.The periodicity is the time from the first repetition of the first PRSresource of a first PRS instance to the same first repetition of thesame first PRS resource of the next PRS instance. The periodicity mayhave a length selected from 2{circumflex over ( )}μ*{4, 5, 8, 10, 16,20, 32, 40, 64, 80, 160, 320, 640, 1280, 2560, 5120, 10240} slots, withμ=0, 1, 2, 3. The repetition factor may have a length selected from {1,2, 4, 6, 8, 16, 32} slots.

A PRS resource ID in a PRS resource set is associated with a single beam(or beam ID) transmitted from a single TRP (where a TRP may transmit oneor more beams). That is, each PRS resource of a PRS resource set may betransmitted on a different beam, and as such, a “PRS resource,” orsimply “resource,” also can be referred to as a “beam.” Note that thisdoes not have any implications on whether the TRPs and the beams onwhich PRS are transmitted are known to the UE.

A “PRS instance” or “PRS occasion” is one instance of a periodicallyrepeated time window (such as a group of one or more consecutive slots)where PRS are expected to be transmitted. A PRS occasion also may bereferred to as a “PRS positioning occasion,” a “PRS positioninginstance, a “positioning occasion,” “a positioning instance,” a“positioning repetition,” or simply an “occasion,” an “instance,” or a“repetition.”

A “positioning frequency layer” (also referred to simply as a “frequencylayer”) is a collection of one or more PRS resource sets across one ormore TRPs that have the same values for certain parameters.Specifically, the collection of PRS resource sets has the samesubcarrier spacing and cyclic prefix (CP) type (meaning all numerologiessupported for the PDSCH are also supported for PRS), the same Point A,the same value of the downlink PRS bandwidth, the same start PRB (andcenter frequency), and the same comb-size. The Point A parameter takesthe value of the parameter “ARFCN-ValueNR” (where “ARFCN” stands for“absolute radio-frequency channel number”) and is an identifier/codethat specifies a pair of physical radio channel used for transmissionand reception. The downlink PRS bandwidth may have a granularity of fourPRBs, with a minimum of 24 PRBs and a maximum of 272 PRBs. Currently, upto four frequency layers have been defined, and up to two PRS resourcesets may be configured per TRP per frequency layer.

The concept of a frequency layer is somewhat like the concept ofcomponent carriers and bandwidth parts (BWPs), but different in thatcomponent carriers and BWPs are used by one base station (or a macrocell base station and a small cell base station) to transmit datachannels, while frequency layers are used by several (usually three ormore) base stations to transmit PRS. A UE may indicate the number offrequency layers it can support when it sends the network itspositioning capabilities, such as during an LTE positioning protocol(LPP) session. For example, a UE may indicate whether it can support oneor four positioning frequency layers.

FIG. 4B illustrates an example of various channels within a downlinkslot of a radio frame. In NR, the channel bandwidth, or systembandwidth, is divided into multiple BWPs. A BWP is a contiguous set ofPRBs selected from a contiguous subset of the common RBs for a givennumerology on a given carrier. Generally, a maximum of four BWPs can bespecified in the downlink and uplink. That is, a UE can be configuredwith up to four BWPs on the downlink, and up to four BWPs on the uplink.Only one BWP (uplink or downlink) may be active at a given time, meaningthe UE may only receive or transmit over one BWP at a time. On thedownlink, the bandwidth of each BWP should be equal to or greater thanthe bandwidth of the SSB, but it may or may not contain the SSB.

Referring to FIG. 4B, a primary synchronization signal (PSS) is used bya UE to determine subframe/symbol timing and a physical layer identity.A secondary synchronization signal (SSS) is used by a UE to determine aphysical layer cell identity group number and radio frame timing. Basedon the physical layer identity and the physical layer cell identitygroup number, the UE can determine a PCI. Based on the PCI, the UE candetermine the locations of the aforementioned DL-RS. The physicalbroadcast channel (PBCH), which carries an MIB, may be logically groupedwith the PSS and SSS to form an SSB (also referred to as an SS/PBCH).The MIB provides a number of RBs in the downlink system bandwidth and asystem frame number (SFN). The physical downlink shared channel (PDSCH)carries user data, broadcast system information not transmitted throughthe PBCH, such as system information blocks (SIBs), and paging messages.

The physical downlink control channel (PDCCH) carries downlink controlinformation (DCI) within one or more control channel elements (CCEs),each CCE including one or more RE group (REG) bundles (which may spanmultiple symbols in the time domain), each REG bundle including one ormore REGs, each REG corresponding to 12 resource elements (one resourceblock) in the frequency domain and one OFDM symbol in the time domain.The set of physical resources used to carry the PDCCH/DCI is referred toin NR as the control resource set (CORESET). In NR, a PDCCH is confinedto a single CORESET and is transmitted with its own DMRS. This enablesUE-specific beamforming for the PDCCH.

In the example of FIG. 4B, there is one CORESET per BWP, and the CORESETspans three symbols (although it may be only one or two symbols) in thetime domain. Unlike LTE control channels, which occupy the entire systembandwidth, in NR, PDCCH channels are localized to a specific region inthe frequency domain (i.e., a CORESET). Thus, the frequency component ofthe PDCCH shown in FIG. 4B is illustrated as less than a single BWP inthe frequency domain. Note that although the illustrated CORESET iscontiguous in the frequency domain, it need not be. In addition, theCORESET may span less than three symbols in the time domain.

The DCI within the PDCCH carries information about uplink resourceallocation (persistent and non-persistent) and descriptions aboutdownlink data transmitted to the UE, referred to as uplink and downlinkgrants, respectively. More specifically, the DCI indicates the resourcesscheduled for the downlink data channel (e.g., PDSCH) and the uplinkdata channel (e.g., PUSCH). Multiple (e.g., up to eight) DCIs can beconfigured in the PDCCH, and these DCIs can have one of multipleformats. For example, there are different DCI formats for uplinkscheduling, for downlink scheduling, for uplink transmit power control(TPC), etc. A PDCCH may be transported by 1, 2, 4, 8, or 16 CCEs inorder to accommodate different DCI payload sizes or coding rates.

The following are the currently supported DCI formats. Format 0-0:fallback for scheduling of PUSCH; Format 0-1: non-fallback forscheduling of PUSCH; Format 1-0: fallback for scheduling of PDSCH;Format 1-1: non-fallback for scheduling of PDSCH; Format 2-0: notifyinga group of UEs of the slot format; Format 2-1: notifying a group of UEsof the PRB(s) and OFDM symbol(s) where the UEs may assume notransmissions are intended for the UEs; Format 2-2: transmission of TPCcommands for PUCCH and PUSCH; and Format 2-3: transmission of a group ofSRS requests and TPC commands for SRS transmissions. Note that afallback format is a default scheduling option that has non-configurablefields and supports basic NR operations. In contrast, a non-fallbackformat is flexible to accommodate NR features.

As will be appreciated, a UE needs to be able to demodulate (alsoreferred to as “decode”) the PDCCH in order to read the DCI, and therebyto obtain the scheduling of resources allocated to the UE on the PDSCHand PUSCH. If the UE fails to demodulate the PDCCH, then the UE will notknow the locations of the PDSCH resources and it will keep attempting todemodulate the PDCCH using a different set of PDCCH candidates insubsequent PDCCH monitoring occasions. If the UE fails to demodulate thePDCCH after some number of attempts, the UE declares a radio linkfailure (RLF). To overcome PDCCH demodulation issues, search spaces areconfigured for efficient PDCCH detection and demodulation.

Generally, a UE does not attempt to demodulate each and very PDCCHcandidate that may be scheduled in a slot. To reduce restrictions on thePDCCH scheduler, and at the same time to reduce the number of blinddemodulation attempts by the UE, search spaces are configured. Searchspaces are indicated by a set of contiguous CCEs that the UE is supposedto monitor for scheduling assignments/grants relating to a certaincomponent carrier. There are two types of search spaces used for thePDCCH to control each component carrier, a common search space (CSS) anda UE-specific search space (USS).

A common search space is shared across all UEs, and a UE-specific searchspace is used per UE (i.e., a UE-specific search space is specific to aspecific UE). For a common search space, a DCI cyclic redundancy check(CRC) is scrambled with a system information radio network temporaryidentifier (SI-RNTI), random access RNTI (RA-RNTI), temporary cell RNTI(TC-RNTI), paging RNTI (P-RNTI), interruption RNTI (INT-RNTI), slotformat indication RNTI (SFI-RNTI), TPC-PUCCH-RNTI, TPC-PUSCH-RNTI,TPC-SRS-RNTI, cell RNTI (C-RNTI), or configured scheduling RNTI(CS-RNTI) for all common procedures. For a UE-specific search space, aDCI CRC is scrambled with a C-RNTI or CS-RNTI, as these are specificallytargeted to individual UE.

A UE demodulates the PDCCH using the four UE-specific search spaceaggregation levels (1, 2, 4, and 8) and the two common search spaceaggregation levels (4 and 8). Specifically, for the UE-specific searchspaces, aggregation level ‘1’ has six PDCCH candidates per slot and asize of six CCEs. Aggregation level ‘2’ has six PDCCH candidates perslot and a size of 12 CCEs. Aggregation level ‘4’ has two PDCCHcandidates per slot and a size of eight CCEs. Aggregation level ‘8’ hastwo PDCCH candidates per slot and a size of 16 CCEs. For the commonsearch spaces, aggregation level ‘4’ has four PDCCH candidates per slotand a size of 16 CCEs. Aggregation level ‘8’ has two PDCCH candidatesper slot and a size of 16 CCEs.

Each search space comprises a group of consecutive CCEs that could beallocated to a PDCCH, referred to as a PDCCH candidate. A UE demodulatesall of the PDCCH candidates in these two search spaces (USS and CSS) todiscover the DCI for that UE. For example, the UE may demodulate the DCIto obtain the scheduled uplink grant information on the PUSCH and thedownlink resources on the PDSCH. Note that the aggregation level is thenumber of REs of a CORESET that carry a PDCCH DCI message, and isexpressed in terms of CCEs. There is a one-to-one mapping between theaggregation level and the number of CCEs per aggregation level. That is,for aggregation level ‘4,’ there are four CCEs. Thus, as shown above, ifthe aggregation level is ‘4’ and the number of PDCCH candidates in aslot is ‘2,’ then the size of the search space is ‘8’ (i.e., 4×2=8).

As illustrated in FIG. 4C, some of the REs (labeled “R”) carry DMRS forchannel estimation at the receiver (e.g., a base station, another UE,etc.). A UE may additionally transmit SRS in, for example, the lastsymbol of a slot. The SRS may have a comb structure, and a UE maytransmit SRS on one of the combs. In the example of FIG. 4C, theillustrated SRS is comb-2 over one symbol. The SRS may be used by a basestation to obtain the channel state information (CSI) for each UE. CSIdescribes how an RF signal propagates from the UE to the base stationand represents the combined effect of scattering, fading, and powerdecay with distance. The system uses the SRS for resource scheduling,link adaptation, massive MIMO, beam management, etc.

Currently, an SRS resource may span 1, 2, 4, 8, or 12 consecutivesymbols within a slot with a comb size of comb-2, comb-4, or comb-8. Thefollowing are the frequency offsets from symbol to symbol for the SRScomb patterns that are currently supported. 1-symbol comb-2: {0};2-symbol comb-2: {0, 1}; 4-symbol comb-2: {0, 1, 0, 1}; 4-symbol comb-4:{0, 2, 1, 3}; 8-symbol comb-4: {0, 2, 1, 3, 0, 2, 1, 3}; 12-symbolcomb-4: {0, 2, 1, 3, 0, 2, 1, 3, 0, 2, 1, 3}; 4-symbol comb-8: {0, 4, 2,6}; 8-symbol comb-8: {0, 4, 2, 6, 1, 5, 3, 7}; and 12-symbol comb-8: {0,4, 2, 6, 1, 5, 3, 7, 0, 4, 2, 6}.

A collection of resource elements that are used for transmission of SRSis referred to as an “SRS resource,” and may be identified by theparameter “SRS-ResourceId.” The collection of resource elements can spanmultiple PRBs in the frequency domain and N (e.g., one or more)consecutive symbol(s) within a slot in the time domain. In a given OFDMsymbol, an SRS resource occupies consecutive PRBs. An “SRS resource set”is a set of SRS resources used for the transmission of SRS signals, andis identified by an SRS resource set ID (“SRS-ResourceSetId”).

Generally, a UE transmits SRS to enable the receiving base station(either the serving base station or a neighboring base station) tomeasure the channel quality between the UE and the base station.However, SRS can also be specifically configured as uplink positioningreference signals for uplink-based positioning procedures, such asuplink time difference of arrival (UL-TDOA), round-trip-time (RTT),uplink angle-of-arrival (UL-AoA), etc. As used herein, the term “SRS”may refer to SRS configured for channel quality measurements or SRSconfigured for positioning purposes. The former may be referred toherein as “SRS-for-communication” and/or the latter may be referred toas “SRS-for-positioning” when needed to distinguish the two types ofSRS.

Several enhancements over the previous definition of SRS have beenproposed for SRS-for-positioning (also referred to as “UL-PRS”), such asa new staggered pattern within an SRS resource (except forsingle-symbol/comb-2), a new comb type for SRS, new sequences for SRS, ahigher number of SRS resource sets per component carrier, and a highernumber of SRS resources per component carrier. In addition, theparameters “SpatialRelationInfo” and “PathLossReference” are to beconfigured based on a downlink reference signal or SSB from aneighboring TRP. Further still, one SRS resource may be transmittedoutside the active BWP, and one SRS resource may span across multiplecomponent carriers. Also, SRS may be configured in RRC connected stateand only transmitted within an active BWP. Further, there may be nofrequency hopping, no repetition factor, a single antenna port, and newlengths for SRS (e.g., 8 and 12 symbols). There also may be open-looppower control and not closed-loop power control, and comb-8 (i.e., anSRS transmitted every eighth subcarrier in the same symbol) may be used.Lastly, the UE may transmit through the same transmit beam from multipleSRS resources for UL-AoA. All of these are features that are additionalto the current SRS framework, which is configured through RRC higherlayer signaling (and potentially triggered or activated through MACcontrol element (CE) or DCI).

FIG. 4D illustrates an example of various channels within an uplink slotof a frame, according to aspects of the disclosure. A random-accesschannel (RACH), also referred to as a physical random-access channel(PRACH), may be within one or more slots within a frame based on thePRACH configuration. The PRACH may include six consecutive RB pairswithin a slot. The PRACH allows the UE to perform initial system accessand achieve uplink synchronization. A physical uplink control channel(PUCCH) may be located on edges of the uplink system bandwidth. ThePUCCH carries uplink control information (UCI), such as schedulingrequests, CSI reports, a channel quality indicator (CQI), a precodingmatrix indicator (PMI), a rank indicator (RI), and HARQ ACK/NACKfeedback. The physical uplink shared channel (PUSCH) carries data, andmay additionally be used to carry a buffer status report (BSR), a powerheadroom report (PHR), and/or UCI.

Note that the terms “positioning reference signal” and “PRS” generallyrefer to specific reference signals that are used for positioning in NRand LTE systems. However, as used herein, the terms “positioningreference signal” and “PRS” may also refer to any type of referencesignal that can be used for positioning, such as but not limited to, PRSas defined in LTE and NR, TRS, PTRS, CRS, CSI-RS, DMRS, PSS, SSS, SSB,SRS, UL-PRS, etc. In addition, the terms “positioning reference signal”and “PRS” may refer to downlink or uplink positioning reference signals,unless otherwise indicated by the context. If needed to furtherdistinguish the type of PRS, a downlink positioning reference signal maybe referred to as a “DL-PRS,” and an uplink positioning reference signal(e.g., an SRS-for-positioning, PTRS) may be referred to as an “UL-PRS.”In addition, for signals that may be transmitted in both the uplink anddownlink (e.g., DMRS, PTRS), the signals may be prepended with “UL” or“DL” to distinguish the direction. For example, “UL-DMRS” may bedifferentiated from “DL-DMRS.”

NR supports a number of cellular network-based positioning technologies,including downlink-based, uplink-based, and downlink-and-uplink-basedpositioning methods. Downlink-based positioning methods include observedtime difference of arrival (OTDOA) in LTE, downlink time difference ofarrival (DL-TDOA) in NR, and downlink angle-of-departure (DL-AoD) in NR.In an OTDOA or DL-TDOA positioning procedure, a UE measures thedifferences between the times of arrival (ToAs) of reference signals(e.g., positioning reference signals (PRS)) received from pairs of basestations, referred to as reference signal time difference (RSTD) or timedifference of arrival (TDOA) measurements, and reports them to apositioning entity. More specifically, the UE receives the identifiers(IDs) of a reference base station (e.g., a serving base station) andmultiple non-reference base stations in assistance data. The UE thenmeasures the RSTD between the reference base station and each of thenon-reference base stations. Based on the known locations of theinvolved base stations and the RSTD measurements, the positioning entitycan estimate the UE's location.

For DL-AoD positioning, the positioning entity uses a beam report fromthe UE of received signal strength measurements of multiple downlinktransmit beams to determine the angle(s) between the UE and thetransmitting base station(s). The positioning entity can then estimatethe location of the UE based on the determined angle(s) and the knownlocation(s) of the transmitting base station(s).

Uplink-based positioning methods include uplink time difference ofarrival (UL-TDOA) and uplink angle-of-arrival (UL-AoA). UL-TDOA issimilar to DL-TDOA, but is based on uplink reference signals (e.g.,sounding reference signals (SRS)) transmitted by the UE. For UL-AoApositioning, one or more base stations measure the received signalstrength of one or more uplink reference signals (e.g., SRS) receivedfrom a UE on one or more uplink receive beams. The positioning entityuses the signal strength measurements and the angle(s) of the receivebeam(s) to determine the angle(s) between the UE and the basestation(s). Based on the determined angle(s) and the known location(s)of the base station(s), the positioning entity can then estimate thelocation of the UE.

Downlink-and-uplink-based positioning methods include enhanced cell-ID(E-CID) positioning and multi-round-trip-time (RTT) positioning (alsoreferred to as “multi-cell RTT”). In an RTT procedure, an initiator (abase station or a UE) transmits an RTT measurement signal (e.g., a PRSor SRS) to a responder (a UE or base station), which transmits an RTTresponse signal (e.g., an SRS or PRS) back to the initiator. The RTTresponse signal includes the difference between the ToA of the RTTmeasurement signal and the transmission time of the RTT response signal,referred to as the reception-to-transmission (Rx-Tx) time difference.The initiator calculates the difference between the transmission time ofthe RTT measurement signal and the ToA of the RTT response signal,referred to as the transmission-to-reception (Tx-Rx) time difference.The propagation time (also referred to as the “time of flight”) betweenthe initiator and the responder can be calculated from the Tx-Rx andRx-Tx time differences. Based on the propagation time and the knownspeed of light, the distance between the initiator and the responder canbe determined. For multi-RTT positioning, a UE performs an RTT procedurewith multiple base stations to enable its location to be determined(e.g., using multilateration) based on the known locations of the basestations. RTT and multi-RTT methods can be combined with otherpositioning techniques, such as UL-AoA and DL-AoD, to improve locationaccuracy.

The E-CID positioning method is based on radio resource management (RRM)measurements. In E-CID, the UE reports the serving cell ID, the timingadvance (TA), and the identifiers, estimated timing, and signal strengthof detected neighbor base stations. The location of the UE is thenestimated based on this information and the known locations of the basestation(s).

To assist positioning operations, a location server (e.g., locationserver 230, LMF 270, SLP 272) may provide assistance data to the UE. Forexample, the assistance data may include identifiers of the basestations (or the cells/TRPs of the base stations) from which to measurereference signals, the reference signal configuration parameters (e.g.,the number of consecutive positioning subframes, periodicity ofpositioning subframes, muting sequence, frequency hopping sequence,reference signal identifier, reference signal bandwidth, etc.), and/orother parameters applicable to the particular positioning method.Alternatively, the assistance data may originate directly from the basestations themselves (e.g., in periodically broadcasted overheadmessages, etc.). in some cases, the UE may be able to detect neighbornetwork nodes itself without the use of assistance data.

In the case of an OTDOA or DL-TDOA positioning procedure, the assistancedata may further include an expected RSTD value and an associateduncertainty, or search window, around the expected RSTD. In some cases,the value range of the expected RSTD may be +/−500 microseconds (μs). Insome cases, when any of the resources used for the positioningmeasurement are in FR1, the value range for the uncertainty of theexpected RSTD may be +/−32 μs. In other cases, when all of the resourcesused for the positioning measurement(s) are in FR2, the value range forthe uncertainty of the expected RSTD may be +/−8 μs.

A location estimate may be referred to by other names, such as aposition estimate, location, position, position fix, fix, or the like. Alocation estimate may be geodetic and comprise coordinates (e.g.,latitude, longitude, and possibly altitude) or may be civic and comprisea street address, postal address, or some other verbal description of alocation. A location estimate may further be defined relative to someother known location or defined in absolute terms (e.g., using latitude,longitude, and possibly altitude). A location estimate may include anexpected error or uncertainty (e.g., by including an area or volumewithin which the location is expected to be included with some specifiedor default level of confidence).

Even when there is no traffic being transmitted from the network to aUE, the UE is expected to monitor every downlink subframe on the PDCCH.This means that the UE has to be “on,” or active, all the time, evenwhen there is no traffic, since the UE does not know exactly when thenetwork will transmit data for it. However, being active all the time isa significant power drain for a UE.

To address this issue, a UE may implement discontinuous reception (DRX)and/or connected-mode discontinuous reception (CDRX) techniques. DRX andCDRX are mechanisms in which a UE goes into a “sleep” mode for ascheduled periods of time and “wakes up” for other periods of time.During the wake, or active, periods, the UE checks to see if there isany data coming from the network, and if there is not, goes back intosleep mode.

To implement DRX and CDRX, the UE and the network need to besynchronized. In a worst-case scenario, the network may attempt to sendsome data to the UE while the UE is in sleep mode, and the UE may wakeup when there is no data to be received. To prevent such scenarios, theUE and the network should have a well-defined agreement about when theUE can be in sleep mode and when the UE should be awake/active. Thisagreement has been standardized in various technical specifications.Note that DRX includes CDRX, and thus, references to DRX refer to bothDRX and CDRX, unless otherwise indicated.

The network (e.g., serving cell) can configure the UE with the DRX/CDRXtiming using an RRC Connection Reconfiguration message (for CDRX) or anRRC Connection Setup message (for DRX). The network can signal thefollowing DRX configuration parameters to the UE:

TABLE 1 DRX Parameter Description DRX Cycle The duration of one ‘ONtime’ plus one ‘OFF time’. (This value is not explicitly specified inRRC messages. This is calculated by the subframe/slot time and “long DRXcycle start offset”). ON Duration The duration of ‘ON time’ within oneDRX cycle. Timer DRX How long a UE should remain ‘ON’ after thereception Inactivity of a PDCCH. When this timer is on, the UE remainsTimer in the ‘ON state,’ which may extend the ON period into the periodthat would be the ‘OFF’ period otherwise. DRX Re- The maximum number ofconsecutive PDCCH transmission subframes/slots a UE should remain activeto wait for Timer an incoming retransmission after the first availableretransmission time. Short DRX A DRX cycle that can be implementedwithin the Cycle ‘OFF’ period of a long DRX cycle. DRX Short Theconsecutive number of subframes/slots that Cycle Timer should follow theshort DRX cycle after the DRX inactivity timer has expired.

FIGS. 5A to 5C illustrate example DRX configurations, according toaspects of the disclosure. FIG. 5A illustrates an example DRXconfiguration 500A in which a long DRX cycle (the time from the start ofone ON duration to the start of the next ON duration) is configured andno PDCCH is received during the cycle. FIG. 5B illustrates an exampleDRX configuration 500B in which a long DRX cycle is configured and aPDCCH is received during an ON duration 510 of the second DRX cycleillustrated. Note that the ON duration 510 ends at time 512. However,the time that the UE is awake/active (the “active time”) is extended totime 514 based on the length of the DRX inactivity timer and the time atwhich the PDCCH is received. Specifically, when the PDCCH is received,the UE starts the DRX inactivity timer and stays in the active stateuntil the expiration of that timer (which is reset each time a PDCCH isreceived during the active time).

FIG. 5C illustrates an example DRX configuration 500C in which a longDRX cycle is configured and a PDCCH and a DRX command MAC controlelement (MAC-CE) are received during an ON duration 520 of the secondDRX cycle illustrated. Note that the active time beginning during ONduration 520 would normally end at time 524 due to the reception of thePDCCH at time 522 and the subsequent expiration of the DRX inactivitytimer at time 524, as discussed above with reference to FIG. 5B.However, in the example of FIG. 5C, the active time is shortened to time526 based on the time at which the DRX command MAC-CE, which instructsthe UE to terminate the DRX inactivity timer and the ON duration timer,is received.

In greater detail, the active time of a DRX cycle is the time duringwhich the UE is considered to be monitoring the PDCCH. The active timemay include the time during which the ON duration timer is running, theDRC inactivity timer is running, the DRX retransmission timer isrunning, the MAC contention resolution timer is running, a schedulingrequest has been sent on the PUCCH and is pending, an uplink grant for apending HARQ retransmission can occur and there is data in thecorresponding HARQ buffer, or a PDCCH indicating a new transmissionaddressed to the cell radio network temporary identifier (C-RNTI) of theUE has not been received after successful reception of a random accessresponse (RAR) for the preamble not selected by the UE. And, innon-contention-based random access, after receiving the RAR, the UEshould be in an active state until the PDCCH indicating new transmissionaddressed to the C-RNTI of the UE is received.

Legacy UE's are expected to monitor all DRX ON durations in their CDRXpattern. In NR, however, the network (e.g., serving base station) cantransmit a wakeup signal (WUS) to a UE during a monitoring occasionahead of a DRX ON duration. A WUS indicates whether or not the UE shouldwake up for the next DRX ON duration. If a UE does not detect a WUSduring the monitoring occasion, it may be preconfigured to either skipthe upcoming ON duration or wakeup for the upcoming ON duration. This isillustrated in FIG. 6 , where the UE is configured to skip the next DRXON duration if it does not detect a WUS.

Specifically, FIG. 6 illustrates a timeline 600 showing two example DRXoccasions (also referred to as “DRX instances,” “DRX cycle occasion,”“DRX cycle instance,” “DRX cycle,” and the like) and their associatedWUS. In the example of FIG. 6 , a WUS is transmitted and received in afirst WUS monitoring occasion (MO) before a first DRX occasion, causingthe UE to wake up and monitor a plurality of PDCCH monitoring occasions(MOs) of the first DRX occasion. However, a WUS is not transmitted ornot received in a second WUS MO before a second DRX occasion, causingthe UE to remain in a DRX sleep state. Using a WUS can provide up to 10percent additional connected mode energy savings for infrequentlyscheduled UEs, depending on the CDRX settings.

FIG. 7 illustrates the operation of a WUS in greater detail.Specifically, FIG. 7 illustrates a comparison between a first WUS thatinstructs a UE to skip the next DRX occasion and a second WUS that doesnot instruct a UE to skip the next DRX occasion. In the example of FIG.7 , a first timeline 700 includes a WUS MO 710 and a DRX ON duration 714separated by a pre-wakeup gap 712, and a second timeline 750 includes aWUS MO 760 and a DRX ON duration 764 separated by a pre-wakeup gap 762.Each DRX ON duration is the beginning of the next DRX cycle. In FIG. 7 ,the horizontal axis represents time and the vertical axis represents thefrequency range monitored by the UE.

In timeline 700, during the WUS MO 710, a WUS is detected that indicatesthat the UE should not wake up for the next DRX cycle, or no WUS isdetected, indicating that the UE should not wake up for the next DRXcycle, depending on how the UE has been configured. As such, the UE doesnot wakeup to monitor the DRX ON duration 714. More specifically, if theMAC entity at the UE is not instructed to wake up by a WUS, the UE doesnot start a DRX ON duration timer for the next single occurrence of theDRX ON duration, i.e., DRX ON duration 714.

In timeline 750, however, during the WUS MO 760, a WUS is detected thatindicates that the UE should wake up for the next DRX cycle, or no WUSis detected, indicating that the UE should wake up for the next DRXcycle (again, depending on how the UE has been configured). As such, theUE wakes up to monitor the DRX ON duration 764. More specifically, ifthe MAC entity at the UE is instructed to wake up by a WUS, the UEstarts the DRX ON duration timer for the next single occurrence of theDRX ON duration, i.e., DRX ON duration 764. In the example of timeline750, a PDCCH 766 is received during the DRX ON duration 764, therebystarting a DRX inactivity timer.

A WUS may be a PDCCH-based signal, and therefore, may be referred to asa “PDCCH-WUS.” More specifically, a WUS is essentially a bit in aWUS-dedicated DCI assigned to a UE. A value of ‘1’ can be configured tomean that the UE should monitor the next (i.e., upcoming) DRX ONduration, and a value of ‘0’ can be configured to mean that the UE canskip the next ON duration.

As illustrated in FIG. 7 , when configured to monitor for WUS, a UEperforms a two-stage wakeup, a low power wakeup for WUS detection and afull power wakeup for PDCCH detection. Such a two-stage wakeupfacilitates a low power implementation for PDCCH-WUS detection because,during the first stage wakeup, the following optimizations are feasible:(1) there is a minimal set of hardware that needs to be brought onlinefor PDCCH-only processing, (2) the operating point in terms of thevoltage levels and clock frequencies of the hardware can be lower, (3)there is a more relaxed PDCCH processing timeline due to the WUS offset(e.g., offline processing), and (4) the receive bandwidth and number ofPDCCH candidates/aggregation levels for the PDCCH-WUS can be reduced.

There are various power saving channel principles that apply to WUS. Forexample, a WUS may be configured on a PCell or primary secondary cell(PSCell) only. In addition, more than one monitoring occasion per DRXcycle can be configured within one or multiple slots. Further, a UE isnot expected to monitor for a WUS during DRX active time. Also, a WUSdoes not impact the parameters “bwp-inactivityTimer,”“dataInactivityTimer,” and “sCellDeactivationTimer.” If the currentactive BWP during DRX operation does not have WUS configuration, or theWUS monitoring occasion is invalid, a UE starts the DRX ON durationtimer for the next DRX occasion. When a WUS is not detected (e.g., dueto discontinuous transmission (DTX) from the base station ormisdetection at the UE), the UE's behavior (whether or not to start theDRX ON duration timer for the next DRX occasion) is configurable.Finally, if both short and long DRX cycles are configured, a WUS may beapplied only to long DRX cycles.

FIG. 8 illustrates an example configuration 800 of a WUS monitoringoccasion. As illustrated in FIG. 8 , a new per-cell-group parameter“PS_offset” is defined. This parameter indicates the earliest potentialstarting point of a WUS monitoring occasion relative to the start of aDRX cycle. This parameter is provided in milliseconds (ms) and has arange of values selected from {0.125, 0.25, 0.5, 1, 2, . . . , N}, whereN is, for example, 15.

A “minimum time gap” (labeled “Gap” in FIG. 8 and occurring at n+3) isdefined as the duration before the start of a DRX cycle, within whichthe UE is not required to monitor for WUS. The minimum time gap is a UEcapability and is provided in units of slots (making it SCS dependent).For a UE capability report, two candidate values per SCS are supported,the largest value of which is no larger than, for example, threemilliseconds.

An existing search space information element (IE) can be used for theconfiguration of a WUS. All parameters of the search space IE (e.g.,duration, “monitoringSymbolsWithinSlot,”“monitoringSlotPeriodicityAndOffset”) can be used without modification.In the example of FIG. 8 , the duration of the WUS is one slot (i.e.,duration=1), which is 14 symbols. The “monitoringSymbolsWithinSlot”indicates that the first two symbols should be monitored. The“monitoringSlotPeriodicityAndOffset” indicates that WUS monitoringoccasions have a periodicity of two slots.

Only the first “full duration” of a WUS at or after the PS_offset, butbefore the DRX ON duration, is monitored. This is illustrated in FIG. 8by graying out all but the highlighted WUS monitoring occasion occurringat slot n. As can be seen in FIG. 8 , the first WUS monitoring occasion,at slot n−2, begins before the PS_offset, and therefore, is notmonitored. The third WUS monitoring occasion, at slot n+2, is notmonitored because, although it is after PS_offset and before the minimumtime gap, it is not the first full WUS monitoring occasion after thePS_offset. The fourth WUS monitoring occasion, at slot n+4, is notmonitored because it occurs during the DRX active time.

A new DCI format and power saving RNTI (PS-RNTI) have been defined forWUS. A PS-RNTI is used to determine if a UE needs to monitor the PDCCHon the next occurrence of the connected mode DRX on-duration. The newDCI format supports multiplexing of one or more UEs. A UE monitors forthe new DCI format only in the CSS (Type-3 CSS is commonly assumed). Forthe new DCI format, a similar UE-specific configuration as DCI format2-0, 2-1, 2-2, and 2-3 is used, such as the total DCI payload size innumber of bits and the starting bit position for the UE-specific fieldin the DCI.

FIG. 9 illustrates an example DCI format 900 for WUS. As shown in FIG. 9, a UE-specific field in the DCI format 900 starts with a one-bit wakeupindicator, immediately followed by ‘X’ bits (configurable) of additionalinformation (labeled as a “Content field”). At the end of the DCI format900 is a CRC with the PS-RNTI. Note that NR supports an SCell dormancybehavior indication in the ‘X’ bits of information.

In some cases, certain uplink transmissions, such as periodic CSIreports on the PUCCH, semi-persistent CSI-reports on the PUCCH/PUSCH,and persistent or semi-persistent SRS, may be scheduled to occur outsideof DRX active time. Without a WUS, the configured behavior is that a UEwill cancel these transmissions when they are scheduled outside DRXactive time. If a UE can receive a WUS, the UE can optionally beconfigured via RRC with an exemption to release (i.e., exempt from theabove cancelation) either all CSI reports on the PUCCH, or selectively,only the Layer 1 RSRP (L1-RSRP) CSI reports on the PUCCH, in certaintime durations. For example, there may be two separate RRC flags, onefor “all” and one for “only L1-RSRP.” The time durations are definedbelow.

A WUS normally causes the receiving UE to skip an entire DRX cycleoccasion (as described above) depending on a “skip”/“do not skip” bit inthe detected WUS payload prior to that DRX occasion. Note that if no WUSpayload is detected (e.g., due to not being transmitted or not beingdetectable), the UE may be configured to either skip or not skip. As aresult of a WUS indicating that the UE should skip the next DRXoccasion, normal DRX active time that would occur during that DRXinstance is skipped.

The time duration for the exemption for CSI (described above) may be theinitial part of a DRX cycle instance that was skipped due to the WUSbehavior described in the preceding paragraph. This initial part iscounted out by the DRX ON duration timer. Note that the actual DRXactive time during a usual DRX cycle where a WUS commanded the UE towake up can be more than this initial part, because if grants arereceived during the cycle, the DRX active time is further extended (asdescribed above with reference to FIGS. 5A to 5C). However, the timeduration for the exemption for CSI covers only the initial part.

Because DL-PRS are typically scheduled by a location server (e.g.,location server 230, LMF 270, SLP 272), while a DRX cycle is typicallyconfigured by the serving base station, there may be times where DL-PRSare scheduled during a DRX sleep time. Accordingly, if DL-PRS are goingto be canceled during DRX off-times (i.e., outside DRX active time),similar exception rules could be defined for DL-PRS reception,SRS-for-positioning transmission, and positioning reports (e.g., L1,MAC-CE, RRC). These different reference signals could have their own RRCconfiguration enable and disable signals, or even dynamic enable anddisable signals that are carried in the WUS payload.

Accordingly, the present disclosure describes UE behavior when a UE isindicated (e.g., by detection or lack of detection of a WUS) to not wakeup for a DRX ON duration during which the UE is otherwiseconfigured/triggered/activated to transmit a positioning measurementreport or an UL-PRS. A positioning measurement report is an uplinkreport containing measurements of DL-PRS (e.g., ToA, RSTD, Rx-Tx timedifference, AoD, AoA, etc.) taken during a downlink ordownlink-and-uplink positioning session, such as a DL-TDOA positioningsession, a multi-RTT positioning session, etc. A positioning measurementreport may also be referred to as a “measurement report,” a “PRSreport,” a “report,” and the like. The UL-PRS may be scheduled to betransmitted as part of an uplink or downlink-and-uplink positioningsession, such as a multi-RTT positioning session, an UL-TDOA positioningsession, etc.

As a first option, the UE may simply not wake up to transmit the PRSreport or the UL-PRS. As a second option, the UE may wake up to transmitthe PRS report or UL-PRS, but may still not expect to receive a DCI ordata, as indicated by the reception, or lack of reception, of a WUS. Asa third option, the UE may wake up to transmit the PRS report or theUL-PRS, and in addition, expect to receive DCI or data as indicated byreception, or lack of reception, of the WUS.

For a positioning measurement report, which of the above three optionsto use may depend on various factors. A first factor may be whether thePRS report is associated with periodic, semi-persistent, or aperiodicDL-PRS. For example, if the measured DL-PRS is/are aperiodic, the UE maywake up (the second and third options), whereas if the DL-PRS is/areperiodic or semi-persistent, the UE would not wake up (the firstoption).

Another factor may be whether the PRS report itself is periodic,semi-persistent, or aperiodic, whether the report is transmitted overLayer 1 (L1) or Layer 3 (L3), and/or the contents of the report (e.g.,TDOA, RSRP, Rx-Tx, AoD, AoA, etc.). For example, if the PRS report is anaperiodic report, then the UE may wake up to send the report, whereas ifthe PRS report is periodic, then the UE may not wake up to send thereport. As another example, if the PRS report is aperiodic, then whetheror not to wake up may depend on indicators in the DCI or RRC signalingthat triggered/configured the report. These factors can be combined withother conditions to create a flexible report pattern.

Another factor may be whether the PRS report contains PRS measurementsof DL-PRS transmitted by a serving base station or a neighboring basestation. For example, for an AoD positioning procedure, the UE may notwake up to report for a neighboring base station.

Another factor may be whether the PRS report is necessary to meet thelink requirement (i.e., the minimum number of base stations from whichthe UE measures DL-PRS) for the positioning method for which the PRSmeasurements are being reported. For example, if before the next DRXcycle the location server (e.g., location server 230, LMF 270, SLP 272)already has PRS measurements for two links but not a third, as neededfor DL-TDOA, the UE may wake up to transmit the PRS report in the nextDRX cycle.

Another factor may be whether the PRS report would contain outdatedmeasurements if the UE did not wake up to transmit the report in thenext DRX ON duration. For example, if the UE sleeps too long, the PRSmeasurement(s) made earlier may no longer be valid due to UE mobility.To report the earlier measurements would result in an inaccuratelocation estimate. As such, the UE may be configured to report PRSmeasurements within some time limit, and if that time limit would expireif the UE does not wake up for the next DRX ON duration, then the UEshould wake up to transmit the PRS report.

Another factor may be the RRC configuration. For example, similar to theRRC configuration defined for a CSI report (e.g., “ps-Periodic CSITransmit” IE, “ps-TransmitPeriodicL1-RSRP” IE), there may be RRC IEsdesigned for PRS reports such as a “ps-Periodic_PRS_Transmit” IE and a“ps-PRS_Transmit_semi-pesistent” IE. In this case, the PRS reportpattern can be (de)activated according to the configuration in these RRCIEs.

Another factor may be whether the specific PRS report is related to aconfigured subset of DL-PRS resources, DL-PRS resource sets, positioningfrequency layers, and/or TRPs for which the UE is expected to pick oneof the three options over another. In this case, the UE should followthe configured option for the related subset of DL-PRS resources, DL-PRSresource sets, positioning frequency layers, and/or TRPs.

Another factor may be the information included in the WUS DCI (i.e., theDCI configuring a UE for WUS operation). For example, the DCI receivedin a DRX active slot may indicate whether or not the UE should wake upto report any DL-PRS measurements performed in that DRX active slot. Asa first method, the DCI bits for the WUS can be a joint bitfield withthe bit(s) for aperiodic CSI report triggering. This means that if thebitfield used for aperiodic CSI reporting indicates that the UE is notexpected to wake up and monitor CSI-RS and/or to report CSI parameters,the UE is also not expected to transmit a PRS report. As a secondmethod, an extra field in the WUS DCI may include a DCI bit that isdedicated for positioning, and may indicate whether or not the UE isexpected to wake up for DL-PRS measuring and reporting.

For UL-PRS, which of the above three options to use may also depend onvarious factors. A first factor may be whether the UL-PRS is associatedwith periodic, semi-persistent, or aperiodic DL-PRS (as for an RTTpositioning procedure). For example, if the DL-PRS is aperiodic, the UEmay wake up to transmit the corresponding UL-PRS (the second and thirdoptions), whereas if the DL-PRS is periodic or semi-persistent, the UEmay not wake up (the first option).

Another factor may be whether the UL-PRS is configured as periodic,semi-persistent, or aperiodic UL-PRS. For example, if the UL-PRS isaperiodic, the UE may wake up to transmit the corresponding UL-PRS (thesecond and third options), whereas if the UL-PRS is periodic orsemi-persistent, the UE may not wake up (the first option).

Another factor may be whether the UL-PRS is necessary to meet the linkrequirement (i.e., the minimum number of base stations to which the UEis expected to transmit UL-PRS) for the positioning method for which theUL-PRS are being transmitted. For example, if before the next DRX cyclethe location server (e.g., location server 230, LMF 270, SLP 272)already has UL-PRS measurements for two links (i.e., measurements ofUL-PRS from two base station) but not a third, as needed for UL-TDOA,the UE may wake up for the UL-PRS transmission in the next DRX ONoccasion.

Another factor may be whether the UL-PRS is targeted towards a servingor neighboring base station. The choice of options may be based on, forexample, a gap in time, power consumption, etc. For example, based onpower consumption concerns (e.g., low battery), the UE may not wake upto transmit UL-PRS.

Another factor may be whether or not the UL-PRS transmission for aneighboring base station is scheduled within DRX active time. Forexample, if UL-PRS for neighboring base stations are only scheduledduring non-DRX active time, transmission may be allowed, so as not toconflict with the serving base station.

Another factor may be whether or not the specific UL-PRS is related to aconfigured subset of UL-PRS resources, UL-PRS resource sets, positioningfrequency layers, and/or TRPs for which the UE is expected to pick oneof the three options over another.

In an aspect, a UE may be configured by the location server (e.g.,location server 230, LMF 270, SLP 272) to wake up to transmit a PRSreport regardless of whether the UE receives a WUS to skip the next DRXcycle. However, whether or not the UE monitors for DCI and/or otherdownlink data (e.g., PDCCH, PDSCH) during the next DRX cycle may dependon the configuration received from the serving base station. This mayresult in a conflict. In this case, there are several options.

As a first option, the location server can inform the serving basestation about the PRS configuration, especially if the PRS report (orUL-PRS transmission) contains non-serving cell related PRS. The servingbase station can then attempt to schedule the DRX cycle accordingly.However, if there is a conflict, then the UE should follow theindication from the serving base station entirely (due to the basestation scheduling the uplink resources). This is also the case foremergent traffic, where the UE should also follow the serving basestation's guidance.

As a second option, the serving base station can signal the WUSconfiguration to the location server. The serving base station maysignal to the location server, separately for each UE (e.g., by adding atimestamp with slot/subframe/frame number), the time at which the UE isconfigured to monitor for a WUS, and the times at which the WUSindicated whether or not to wake up for the next DRX ON duration. Thelocation server can then assign/configure PRS resources and PRS reportsaccordingly.

As a third option, the location server can configure PRS and the servingbase station can configure DRX and WUS. Which the UE follows may dependon the configuration received. For example, if the UE receives an RRCconfiguration (i.e., from the serving base station), then the UE shouldfollow the configuration from the serving base station. If the UEreceives a WUS, it should follow the configuration from the serving basestation. If the UE receives an aperiodic PRS, it should follow theconfiguration from the location server, and so on.

FIG. 10 illustrates an example method 1000 of wireless communication,according to aspects of the disclosure. In an aspect, method 1000 may beperformed by a UE (e.g., any of the UEs described herein).

At 1010, the UE determines (e.g., based on detection of a WUS, or lackof detection of a WUS) that the UE is not expected to wake up during thenext DRX ON duration of a DRX cycle. In an aspect, operation 1010 may beperformed by the one or more WWAN transceivers 310, the one or moreprocessors 332, memory 340, and/or positioning component 342, any or allof which may be considered means for performing this operation.

At 1020, the UE determines, based on one or more factors that aredescribed in detail above and below, whether to wake up during the nextDRX ON duration to transmit a positioning measurement report or anUL-PRS. In an aspect, operation 1020 may be performed by the one or moreWWAN transceivers 310, the one or more processors 332, memory 340,and/or positioning component 342, any or all of which may be consideredmeans for performing this operation.

At 1030, based on the determination, the UE either wakes up andtransmits the positioning measurement report or the UL-PRS during thenext DRX ON duration, or remains in a DRX sleep state and refrains fromtransmitting the positioning measurement report or the UL-PRS during thenext DRX ON duration. In an aspect, operation 1030 may be performed bythe one or more WWAN transceivers 310, the one or more processors 332,memory 340, and/or positioning component 342, any or all of which may beconsidered means for performing this operation.

As will be appreciated, a technical advantage of the method 1000 isenabling the UE to determine how to handle the transmission of apositioning measurement report or UL-PRS when the UE is not scheduled towake up during the next DRX ON duration, thereby providing flexibilityto choose either power savings (no transmission) or better positioningperformance.

In the detailed description above it can be seen that different featuresare grouped together in examples. This manner of disclosure should notbe understood as an intention that the example clauses have morefeatures than are explicitly mentioned in each clause. Rather, thevarious aspects of the disclosure may include fewer than all features ofan individual example clause disclosed. Therefore, the following clausesshould hereby be deemed to be incorporated in the description, whereineach clause by itself can stand as a separate example. Although eachdependent clause can refer in the clauses to a specific combination withone of the other clauses, the aspect(s) of that dependent clause are notlimited to the specific combination. It will be appreciated that otherexample clauses can also include a combination of the dependent clauseaspect(s) with the subject matter of any other dependent clause orindependent clause or a combination of any feature with other dependentand independent clauses. The various aspects disclosed herein expresslyinclude these combinations, unless it is explicitly expressed or can bereadily inferred that a specific combination is not intended (e.g.,contradictory aspects, such as defining an element as both an insulatorand a conductor). Furthermore, it is also intended that aspects of aclause can be included in any other independent clause, even if theclause is not directly dependent on the independent clause.

Implementation examples are described in the following numbered clauses:

Clause 1. A method of wireless communication performed by a userequipment (UE) operating in discontinuous reception (DRX) mode,comprising: determining that the UE is not expected to wake up during anext DRX ON duration of a DRX cycle; determining, based on one or morefactors, whether to wake up during the next DRX ON duration to transmita downlink positioning reference signal (DL-PRS) measurement report oran uplink PRS (UL-PRS); and based on the determination: waking up andtransmitting the DL-PRS measurement report or the UL-PRS during the nextDRX ON duration, or remaining in a DRX sleep state and refraining fromtransmitting the DL-PRS measurement report or the UL-PRS during the nextDRX ON duration.

Clause 2. The method of clause 1, wherein the determining comprisesdetermining whether to wake up during the next DRX ON duration totransmit the DL-PRS measurement report.

Clause 3. The method of clause 2, wherein one of the one or more factorscomprises whether or not the DL-PRS measurement report containsmeasurements of periodic, semi-persistent, or aperiodic DL-PRS.

Clause 4. The method of any of clauses 2 to 3, wherein one of the one ormore factors comprises whether or not the DL-PRS measurement report isperiodic, semi-persistent, or aperiodic.

Clause 5. The method of any of clauses 2 to 4, wherein one of the one ormore factors comprises whether or not the DL-PRS measurement report istransmitted over Layer 1 or Layer 3.

Clause 6. The method of any of clauses 2 to 5, wherein one of the one ormore factors comprises a type of a positioning session for which theDL-PRS measurement report is being transmitted.

Clause 7. The method of any of clauses 2 to 6, wherein one of the one ormore factors comprises whether or not the DL-PRS measurement reportcontains PRS measurements of DL-PRS transmitted by a serving basestation or a neighboring base station.

Clause 8. The method of any of clauses 2 to 7, wherein one of the one ormore factors comprises whether or not the DL-PRS measurement report isnecessary to meet a link requirement for a positioning method for whichthe DL-PRS measurement report is being transmitted.

Clause 9. The method of any of clauses 2 to 8, wherein one of the one ormore factors comprises whether or not the DL-PRS measurement reportwould contain outdated measurements if the UE does not wake up totransmit the DL-PRS measurement report in the next DRX ON duration.

Clause 10. The method of any of clauses 2 to 9, wherein one of the oneor more factors comprises whether or not a radio resource control (RRC)configuration from a serving base station instructs the UE to wake upfor the next DRX ON duration.

Clause 11. The method of any of clauses 2 to 10, wherein one of the oneor more factors comprises whether or not the DL-PRS measurement reportis associated with a subset of DL-PRS resources, DL-PRS resource sets,positioning frequency layers, and/or transmission-reception points(TRPs) for which the UE is expected to transmit a DL-PRS measurementreport or refrain from transmitting a DL-PRS measurement report.

Clause 12. The method of any of clauses 2 to 11, wherein: one of the oneor more factors comprises information received in downlink controlinformation (DCI) received in a previous DRX active slot, and theinformation comprises an indication of whether or not to reportmeasurements of DL-PRS performed in the previous DRX active slot in thenext DRX ON duration.

Clause 13. The method of clause 12, wherein: the information comprisesone or more bits configuring the UE to wake up to transmit or monitor achannel state information reference signal (CSI-RS), or the informationcomprises one or more bits configuring the UE to wake up to transmit theDL-PRS measurement report.

Clause 14. The method of any of clauses 1 to 13, wherein the determiningcomprises determining whether to wake up during the next DRX ON durationto transmit the UL-PRS.

Clause 15. The method of clause 14, wherein one of the one or morefactors comprises whether or not the UL-PRS is associated with periodic,semi-persistent, or aperiodic DL-PRS.

Clause 16. The method of any of clauses 14 to 15, wherein one of the oneor more factors comprises whether or not the UL-PRS is periodic,semi-persistent, or aperiodic.

Clause 17. The method of any of clauses 14 to 16, wherein one of the oneor more factors comprises whether or not the UL-PRS is necessary to meeta link requirement for a positioning method for which the UL-PRS isbeing transmitted.

Clause 18. The method of any of clauses 14 to 17, wherein one of the oneor more factors comprises whether or not the UL-PRS is targeted towardsa serving base station or a neighboring base station.

Clause 19. The method of any of clauses 14 to 18, wherein one of the oneor more factors comprises whether or not UL-PRS for neighboring basestations are only scheduled outside of DRX active time.

Clause 20. The method of any of clauses 14 to 19, wherein one of the oneor more factors comprises whether or not the UL-PRS is related to aconfigured subset of UL-PRS resources, UL-PRS resource sets, positioningfrequency layers, and/or TRPs for which the UE is expected to transmitUL-PRS or refrain from transmitting UL-PRS.

Clause 21. The method of any of clauses 1 to 20, wherein, based on theUE waking up and transmitting the DL-PRS measurement report or theUL-PRS during the next DRX ON duration, the UE does not expect toreceive DCI or downlink data during the next DRX ON duration.

Clause 22. The method of any of clauses 1 to 20, wherein, based on theUE waking up and transmitting the DL-PRS measurement report or theUL-PRS during the next DRX ON duration, the UE expects to receive DCI ordownlink data during the next DRX ON duration.

Clause 23. The method of any of clauses 1 to 22, further comprising:receiving, from a location server, a configuration to wake up andtransmit the DL-PRS measurement report or the UL-PRS regardless of thedetermination that the UE is not expected to wake up during the next DRXON duration; and receiving, from a serving base station, a configurationof whether or not to monitor for DCI or downlink data during the nextDRX ON duration based on waking up to transmit the DL-PRS measurementreport or the UL-PRS.

Clause 24. The method of clause 23, wherein, based on a conflict betweenthe configuration from the location server and the configuration fromthe serving base station, the UE follows the configuration from theserving base station.

Clause 25. The method of any of clauses 23 to 24, wherein theconfiguration from the location server is provided to the serving basestation to enable the serving base station to schedule the DRX cycleaccordingly.

Clause 26. The method of any of clauses 23 to 25, wherein theconfiguration from the base station is provided to the location serverto enable the location server to schedule PRS resources and DL-PRSmeasurement reports accordingly.

Clause 27. The method of any of clauses 23 to 26, wherein the locationserver configures DL-PRS and the serving base station configures the DRXcycle and wakeup signals (WUS) associated with the DRX mode.

Clause 28. The method of any of clauses 1 to 27, wherein the determiningthat the UE is not expected to wake up during the next DRX ON durationcomprises: receiving a wakeup signal (WUS) within a pre-wakeup gapbefore the next DRX ON duration.

Clause 29. The method of any of clauses 1 to 27, wherein the determiningthat the UE is not expected to wake up during the next DRX ON durationcomprises: failing to detect a WUS within a pre-wakeup gap before thenext DRX ON duration.

Clause 30. The method of any of clauses 1 to 27, wherein the determiningthat the UE is not expected to wake up during the next DRX ON durationcomprises: receiving an RRC information element (IE) during a previousDRX active time indicating that the UE is not expected to wake up duringthe next DRX ON duration.

Clause 31. The method of any of clauses 1 to 27, wherein the determiningthat the UE is not expected to wake up during the next DRX ON durationcomprises: receiving DCI during a previous DRX active time indicatingthat the UE is not expected to wake up during the next DRX ON duration.

Clause 32. An apparatus comprising a memory, a transceiver, and aprocessor communicatively coupled to the memory and the transceiver, thememory, the transceiver, and the processor configured to perform amethod according to any of clauses 1 to 31.

Clause 33. An apparatus comprising means for performing a methodaccording to any of clauses 1 to 31.

Clause 34. A non-transitory computer-readable medium storingcomputer-executable instructions, the computer-executable comprising atleast one instruction for causing a computer or processor to perform amethod according to any of clauses 1 to 31.

Additional implementation examples are described in the followingnumbered clauses:

Clause 1. A method of wireless communication performed by a userequipment (UE) operating in discontinuous reception (DRX) mode,comprising: determining that the UE is not expected to wake up during anext DRX ON duration of a DRX cycle; determining, based on one or morefactors, whether to wake up during the next DRX ON duration to transmita positioning measurement report or an uplink positioning referencesignal (UL-PRS); and based on the determination: waking up andtransmitting the positioning measurement report or the UL-PRS during thenext DRX ON duration, or remaining in a DRX sleep state and refrainingfrom transmitting the positioning measurement report or the UL-PRSduring the next DRX ON duration.

Clause 2. The method of clause 1, wherein the determining, based on theone or more factors, whether to wake up comprises determining whether towake up during the next DRX ON duration to transmit the positioningmeasurement report.

Clause 3. The method of clause 2, wherein one of the one or more factorscomprises whether or not the positioning measurement report containsmeasurements derived based on periodic, semi-persistent, or aperiodicdownlink positioning reference signals (DL-PRS).

Clause 4. The method of any of clauses 2 to 3, wherein one of the one ormore factors comprises whether or not the positioning measurement reportis periodic, semi-persistent, or aperiodic.

Clause 5. The method of any of clauses 2 to 4, wherein one of the one ormore factors comprises whether or not the positioning measurement reportis transmitted over Layer 1 or Layer 3.

Clause 6. The method of any of clauses 2 to 5, wherein one of the one ormore factors comprises a type of a positioning session for which thepositioning measurement report is being transmitted.

Clause 7. The method of any of clauses 2 to 6, wherein one of the one ormore factors comprises whether or not the positioning measurement reportcontains PRS measurements of DL-PRS transmitted by a serving basestation or a neighboring base station.

Clause 8. The method of any of clauses 2 to 7, wherein one of the one ormore factors comprises whether or not the positioning measurement reportwould contain outdated measurements if the UE does not wake up totransmit the positioning measurement report in the next DRX ON duration.

Clause 9. The method of any of clauses 2 to 8, wherein one of the one ormore factors comprises whether or not a radio resource control (RRC)configuration from a serving base station instructs the UE to wake upfor the next DRX ON duration.

Clause 10. The method of any of clauses 2 to 9, wherein: one of the oneor more factors comprises information received in downlink controlinformation (DCI) received in a previous DRX active slot, and theinformation comprises an indication of whether or not to reportmeasurements of DL-PRS performed in the previous DRX active slot in thenext DRX ON duration.

Clause 11. The method of clause 10, wherein: the information comprisesone or more bits configuring the UE to wake up to transmit or monitor achannel state information reference signal (CSI-RS), or the informationcomprises one or more bits configuring the UE to wake up to transmit thepositioning measurement report.

Clause 12. The method of any of clauses 1 to 11, wherein thedetermining, based on the one or more factors, whether to wake upcomprises determining whether to wake up during the next DRX ON durationto transmit the UL-PRS.

Clause 13. The method of clause 12, wherein one of the one or morefactors comprises whether or not the UL-PRS is associated with periodic,semi-persistent, or aperiodic DL-PRS.

Clause 14. The method of any of clauses 12 to 13, wherein one of the oneor more factors comprises whether or not the UL-PRS is periodic,semi-persistent, or aperiodic.

Clause 15. The method of any of clauses 12 to 14, wherein one of the oneor more factors comprises whether or not the UL-PRS is associated with aspatial transmit relation, a pathloss reference, or both from a servingbase station or a neighboring base station.

Clause 16. The method of any of clauses 12 to 15, wherein one of the oneor more factors comprises whether or not UL-PRS for neighboring basestations are only scheduled outside of DRX active time.

Clause 17. The method of any of clauses 12 to 16, wherein one of the oneor more factors comprises whether or not the UL-PRS is related to aconfigured subset of UL-PRS resources, UL-PRS resource sets, positioningfrequency layers, and/or TRPs for which the UE is expected to transmitUL-PRS or refrain from transmitting UL-PRS.

Clause 18. The method of any of clauses 1 to 17, wherein, based on theUE waking up and transmitting the positioning measurement report or theUL-PRS during the next DRX ON duration: the UE does not expect toreceive DCI or downlink data during the next DRX ON duration, or the UEexpects to receive DCI or downlink data during the next DRX ON duration.

Clause 19. The method of any of clauses 1 to 18, further comprising:receiving, from a location server, a configuration to wake up andtransmit the positioning measurement report or the UL-PRS regardless ofa determination that the UE is not expected to wake up during the nextDRX ON duration; and receiving, from a serving base station, aconfiguration of whether or not to monitor for DCI or downlink dataduring the next DRX ON duration based on waking up to transmit thepositioning measurement report or the UL-PRS, wherein, based on aconflict between the configuration from the location server and theconfiguration from the serving base station, the UE follows theconfiguration from the serving base station.

Clause 20. The method of clause 19, wherein: the configuration from thelocation server is provided to the serving base station to enable theserving base station to schedule the DRX cycle accordingly, and theconfiguration from the serving base station is provided to the locationserver to enable the location server to schedule PRS resources andpositioning measurement reports accordingly.

Clause 21. An apparatus comprising a memory, at least one transceiver,and at least one processor communicatively coupled to the memory and theat least one transceiver, the memory, the at least one transceiver, andthe at least one processor configured to perform a method according toany of clauses 1 to 20.

Clause 22. An apparatus comprising means for performing a methodaccording to any of clauses 1 to 20.

Clause 23. A non-transitory computer-readable medium storingcomputer-executable instructions, the computer-executable comprising atleast one instruction for causing a computer or processor to perform amethod according to any of clauses 1 to 20.

Those of skill in the art will appreciate that information and signalsmay be represented using any of a variety of different technologies andtechniques. For example, data, instructions, commands, information,signals, bits, symbols, and chips that may be referenced throughout theabove description may be represented by voltages, currents,electromagnetic waves, magnetic fields or particles, optical fields orparticles, or any combination thereof.

Further, those of skill in the art will appreciate that the variousillustrative logical blocks, modules, circuits, and algorithm stepsdescribed in connection with the aspects disclosed herein may beimplemented as electronic hardware, computer software, or combinationsof both. To clearly illustrate this interchangeability of hardware andsoftware, various illustrative components, blocks, modules, circuits,and steps have been described above generally in terms of theirfunctionality. Whether such functionality is implemented as hardware orsoftware depends upon the particular application and design constraintsimposed on the overall system. Skilled artisans may implement thedescribed functionality in varying ways for each particular application,but such implementation decisions should not be interpreted as causing adeparture from the scope of the present disclosure.

The various illustrative logical blocks, modules, and circuits describedin connection with the aspects disclosed herein may be implemented orperformed with a general purpose processor, a digital signal processor(DSP), an ASIC, a field-programable gate array (FPGA), or otherprogrammable logic device, discrete gate or transistor logic, discretehardware components, or any combination thereof designed to perform thefunctions described herein. A general-purpose processor may be amicroprocessor, but in the alternative, the processor may be anyconventional processor, controller, microcontroller, or state machine. Aprocessor may also be implemented as a combination of computing devices,for example, a combination of a DSP and a microprocessor, a plurality ofmicroprocessors, one or more microprocessors in conjunction with a DSPcore, or any other such configuration.

The methods, sequences and/or algorithms described in connection withthe aspects disclosed herein may be embodied directly in hardware, in asoftware module executed by a processor, or in a combination of the two.A software module may reside in random access memory (RAM), flashmemory, read-only memory (ROM), erasable programmable ROM (EPROM),electrically erasable programmable ROM (EEPROM), registers, hard disk, aremovable disk, a CD-ROM, or any other form of storage medium known inthe art. An example storage medium is coupled to the processor such thatthe processor can read information from, and write information to, thestorage medium. In the alternative, the storage medium may be integralto the processor. The processor and the storage medium may reside in anASIC. The ASIC may reside in a user terminal (e.g., UE). In thealternative, the processor and the storage medium may reside as discretecomponents in a user terminal.

In one or more example aspects, the functions described may beimplemented in hardware, software, firmware, or any combination thereof.If implemented in software, the functions may be stored on ortransmitted over as one or more instructions or code on acomputer-readable medium. Computer-readable media includes both computerstorage media and communication media including any medium thatfacilitates transfer of a computer program from one place to another. Astorage media may be any available media that can be accessed by acomputer. By way of example, and not limitation, such computer-readablemedia can comprise RAM, ROM, EEPROM, CD-ROM or other optical diskstorage, magnetic disk storage or other magnetic storage devices, or anyother medium that can be used to carry or store desired program code inthe form of instructions or data structures and that can be accessed bya computer. Also, any connection is properly termed a computer-readablemedium. For example, if the software is transmitted from a website,server, or other remote source using a coaxial cable, fiber optic cable,twisted pair, digital subscriber line (DSL), or wireless technologiessuch as infrared, radio, and microwave, then the coaxial cable, fiberoptic cable, twisted pair, DSL, or wireless technologies such asinfrared, radio, and microwave are included in the definition of medium.Disk and disc, as used herein, includes compact disc (CD), laser disc,optical disc, digital versatile disc (DVD), floppy disk and Blu-ray discwhere disks usually reproduce data magnetically, while discs reproducedata optically with lasers. Combinations of the above should also beincluded within the scope of computer-readable media.

While the foregoing disclosure shows illustrative aspects of thedisclosure, it should be noted that various changes and modificationscould be made herein without departing from the scope of the disclosureas defined by the appended claims. The functions, steps and/or actionsof the method claims in accordance with the aspects of the disclosuredescribed herein need not be performed in any particular order.Furthermore, although elements of the disclosure may be described orclaimed in the singular, the plural is contemplated unless limitation tothe singular is explicitly stated.

What is claimed is:
 1. A method of wireless communication performed by auser equipment (UE) operating in discontinuous reception (DRX) mode,comprising: determining that the UE is not expected to wake up during anext DRX ON duration of a DRX cycle; determining, based on one or morefactors, whether to wake up during the next DRX ON duration to transmita positioning measurement report or an uplink positioning referencesignal (UL-PRS) during the next DRX ON duration; and based on thedetermination to wake up: waking up and transmitting the positioningmeasurement report or the UL-PRS during the next DRX ON duration, orremaining in a DRX sleep state and refraining from transmitting thepositioning measurement report or the UL-PRS during the next DRX ONduration.
 2. The method of claim 1, wherein the determining, based onthe one or more factors, whether to wake up comprises determiningwhether to wake up during the next DRX ON duration to transmit thepositioning measurement report.
 3. The method of claim 2, wherein one ofthe one or more factors comprises whether or not the positioningmeasurement report contains measurements derived based on periodic,semi-persistent, or aperiodic downlink positioning reference signals(DL-PRS).
 4. The method of claim 2, wherein one of the one or morefactors comprises whether or not the positioning measurement report isperiodic, semi-persistent, or aperiodic.
 5. The method of claim 2,wherein one of the one or more factors comprises whether or not thepositioning measurement report is transmitted over Layer 1 or Layer 3.6. The method of claim 2, wherein one of the one or more factorscomprises a type of a positioning session for which the positioningmeasurement report is being transmitted.
 7. The method of claim 2,wherein one of the one or more factors comprises whether or not thepositioning measurement report contains PRS measurements of DL-PRStransmitted by a serving base station or a neighboring base station. 8.The method of claim 2, wherein one of the one or more factors compriseswhether or not the positioning measurement report would contain outdatedmeasurements if the UE does not wake up to transmit the positioningmeasurement report in the next DRX ON duration.
 9. The method of claim2, wherein one of the one or more factors comprises whether or not aradio resource control (RRC) configuration from a serving base stationinstructs the UE to wake up for the next DRX ON duration.
 10. The methodof claim 2, wherein: one of the one or more factors comprisesinformation received in downlink control information (DCI) received in aprevious DRX active slot, and the information comprises an indication ofwhether or not to report measurements of DL-PRS performed in theprevious DRX active slot in the next DRX ON duration.
 11. The method ofclaim 10, wherein: the information comprises one or more bitsconfiguring the UE to wake up to transmit or monitor a channel stateinformation reference signal (CSI-RS), or the information comprises oneor more bits configuring the UE to wake up to transmit the positioningmeasurement report.
 12. The method of claim 1, wherein the determining,based on the one or more factors, whether to wake up comprisesdetermining whether to wake up during the next DRX ON duration totransmit the UL-PRS.
 13. The method of claim 12, wherein one of the oneor more factors comprises whether or not the UL-PRS is associated withperiodic, semi-persistent, or aperiodic DL-PRS.
 14. The method of claim12, wherein one of the one or more factors comprises whether or not theUL-PRS is periodic, semi-persistent, or aperiodic.
 15. The method ofclaim 12, wherein one of the one or more factors comprises whether ornot the UL-PRS is associated with a spatial transmit relation, apathloss reference, or both from a serving base station or a neighboringbase station.
 16. The method of claim 12, wherein one of the one or morefactors comprises whether or not UL-PRS for neighboring base stationsare only scheduled outside of DRX active time.
 17. The method of claim12, wherein one of the one or more factors comprises whether or not theUL-PRS is related to a configured subset of UL-PRS resources, UL-PRSresource sets, positioning frequency layers, and/or TRPs for which theUE is expected to transmit UL-PRS or refrain from transmitting UL-PRS.18. The method of claim 1, wherein, based on the UE waking up andtransmitting the positioning measurement report or the UL-PRS during thenext DRX ON duration: the UE does not expect to receive DCI or downlinkdata during the next DRX ON duration, or the UE expects to receive DCIor downlink data during the next DRX ON duration.
 19. The method ofclaim 1, further comprising: receiving, from a location server, aconfiguration to wake up and transmit the positioning measurement reportor the UL-PRS regardless of a determination that the UE is not expectedto wake up during the next DRX ON duration; and receiving, from aserving base station, a configuration of whether or not to monitor forDCI or downlink data during the next DRX ON duration based on waking upto transmit the positioning measurement report or the UL-PRS, wherein,based on a conflict between the configuration from the location serverand the configuration from the serving base station, the UE follows theconfiguration from the serving base station.
 20. The method of claim 19,wherein: the configuration from the location server is provided to theserving base station to enable the serving base station to schedule theDRX cycle accordingly, and the configuration from the serving basestation is provided to the location server to enable the location serverto schedule PRS resources and positioning measurement reportsaccordingly.
 21. A user equipment (UE), comprising: a memory; at leastone transceiver; and at least one processor communicatively coupled tothe memory and the at least one transceiver, the at least one processorconfigured to, while operating in discontinuous reception (DRX) mode:determine that the UE is not expected to wake up during a next DRX ONduration of a DRX cycle; determine, based on one or more factors,whether to wake up during the next DRX ON duration to transmit apositioning measurement report or an uplink positioning reference signal(UL-PRS) during the next DRX ON duration; and based on the determinationto wake up: wake up and cause the at least one transceiver to transmitthe positioning measurement report or the UL-PRS during the next DRX ONduration, or remain in a DRX sleep state and refrain from causing the atleast one transceiver to transmit the positioning measurement report orthe UL-PRS during the next DRX ON duration.
 22. The UE of claim 21,wherein the at least one processor being configured to determine, basedon the one or more factors, whether to wake up comprises the at leastone processor being configured to determine whether to wake up duringthe next DRX ON duration to transmit the positioning measurement report.23. The UE of claim 22, wherein: one of the one or more factorscomprises whether or not the positioning measurement report containsmeasurements of periodic, semi-persistent, or aperiodic downlinkpositioning reference signal (DL-PRS), one of the one or more factorscomprises whether or not the positioning measurement report is periodic,semi-persistent, or aperiodic, one of the one or more factors compriseswhether or not the positioning measurement report is transmitted overLayer 1 or Layer 3, one of the one or more factors comprises a type of apositioning session for which the positioning measurement report isbeing transmitted, one of the one or more factors comprises whether ornot the positioning measurement report contains PRS measurements ofDL-PRS transmitted by a serving base station or a neighboring basestation, one of the one or more factors comprises whether or not thepositioning measurement report would contain outdated measurements ifthe UE does not wake up to transmit the positioning measurement reportin the next DRX ON duration, one of the one or more factors compriseswhether or not a radio resource control (RRC) configuration from theserving base station instructs the UE to wake up for the next DRX ONduration, or any combination thereof.
 24. The UE of claim 22, wherein:one of the one or more factors comprises information received indownlink control information (DCI) received in a previous DRX activeslot, and the information comprises an indication of whether or not toreport measurements of DL-PRS performed in the previous DRX active slotin the next DRX ON duration.
 25. The UE of claim 24, wherein: theinformation comprises one or more bits configuring the UE to wake up totransmit or monitor a channel state information reference signal(CSI-RS), or the information comprises one or more bits configuring theUE to wake up to transmit the positioning measurement report.
 26. The UEof claim 21, wherein the at least one processor being configured todetermine, based on the one or more factors, whether to wake upcomprises the at least one processor being configured to determinewhether to wake up during the next DRX ON duration to transmit theUL-PRS.
 27. The UE of claim 26, wherein: one of the one or more factorscomprises whether or not the UL-PRS is associated with periodic,semi-persistent, or aperiodic DL-PRS, one of the one or more factorscomprises whether or not the UL-PRS is periodic, semi-persistent, oraperiodic, one of the one or more factors comprises whether or not theUL-PRS is targeted towards a serving base station or a neighboring basestation, one of the one or more factors comprises whether or not UL-PRSfor neighboring base stations are only scheduled outside of DRX activetime, one of the one or more factors comprises whether or not the UL-PRSis related to a configured subset of UL-PRS resources, UL-PRS resourcesets, positioning frequency layers, and/or TRPs for which the UE isexpected to transmit UL-PRS or refrain from transmitting UL-PRS, or anycombination thereof.
 28. The UE of claim 21, wherein the at least oneprocessor is further configured to: receive, from a location server viathe at least one transceiver, a configuration to wake up and transmitthe positioning measurement report or the UL-PRS regardless of adetermination that the UE is not expected to wake up during the next DRXON duration; and receive, from a serving base station via the at leastone transceiver, a configuration of whether or not to monitor for DCI ordownlink data during the next DRX ON duration based on waking up totransmit the positioning measurement report or the UL-PRS, wherein,based on a conflict between the configuration from the location serverand the configuration from the serving base station, the at least oneprocessor follows the configuration from the serving base station.
 29. Auser equipment (UE), comprising: means for determining, while operatingin discontinuous reception (DRX) mode, that the UE is not expected towake up during a next DRX ON duration of a DRX cycle; means fordetermining, based on one or more factors, whether to wake up during thenext DRX ON duration to transmit a positioning measurement report or anuplink positioning reference signal (UL-PRS) during the next DRX ONduration; and based on the determination to wake up: means for waking upand transmitting the positioning measurement report or the UL-PRS duringthe next DRX ON duration, or means for remaining in a DRX sleep stateand refraining from transmitting the positioning measurement report orthe UL-PRS during the next DRX ON duration.
 30. A non-transitorycomputer-readable medium storing computer-executable instructions, thecomputer-executable instructions comprising: at least one instructioninstructing a user equipment (UE) operating in discontinuous reception(DRX) mode to determine that the UE is not expected to wake up during anext DRX ON duration of a DRX cycle; at least one instructioninstructing the UE to determine, based on one or more factors, whetherto wake up during the next DRX ON duration to transmit a positioningmeasurement report or an uplink positioning reference signal (UL-PRS)during the next DRX ON duration; and based on the determination to wakeup: at least one instruction instructing the UE to wake up and transmitthe positioning measurement report or the UL-PRS during the next DRX ONduration, or at least one instruction instructing the UE to remain in aDRX sleep state and refrain from transmitting the positioningmeasurement report or the UL-PRS during the next DRX ON duration.